Talk:File extension is in extensions list: Difference between revisions

→‎Differing definitions of 'extension': Not sure about the definition
m (→‎Dupe?: corrected misspellings, clarified list of filenames without an extension from those that do.)
(→‎Differing definitions of 'extension': Not sure about the definition)
 
Line 29:
 
By the usual Unix Way of thinking, the OS and shells are largely agnostic to the notion of filename extension, so each individual program will interpret the idea as it sees fit. I see only two constraints: first, the convention that an extension must start with the final period in a filename, and second, that an extension cannot contain characters that are illegal in a filename, namely / or the null character. Other than that, it's perfectly legal to have characters like ½ or space in a filename, and the extension is no different from the rest of the filename in that regard. (Usual caveats, of course, since most filesystems haven't a clue what that you've encoded a Unicode character, and if you use spaces in an extension for your program, we will hunt you down and kill you. <tt>:)</tt> --[[User:TimToady|TimToady]] ([[User talk:TimToady|talk]]) 00:31, 13 August 2014 (UTC)
 
: The extension ''might'' start at the ''first'' period. But let's not worry too much about that; this task has the benefit of being something that matches up with the sorts of things that many programmers want to do when starting out with a programming language. –[[User:Dkf|Donal Fellows]] ([[User talk:Dkf|talk]]) 13:16, 30 August 2014 (UTC)
 
== Programs violating the first sentence? ==
Anonymous user