Talk:Extract file extension: Difference between revisions
→Use Libraries not Footguns
m (→definition of a legal file extension: added a name in case the glyph doesn't render properly.) |
|||
| (9 intermediate revisions by 5 users not shown) | |||
Line 23:
'''<big><big><math>\pi</math></big></big>''' (pi) is a number, so is '''+1.5''' and '''-6'''. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 23:42, 4 May 2015 (UTC)
Another also:
The 2nd part of the definition of a filename extension states that:
* consists of a period, followed by one or more ASCII letters or digits (A-Z, a-z, 0-9)
I would argue that the filename
abc._#5
fits that requirement as the numeral '''5''' follows the period.
Therefore, the following would be more apt:
* consists of a period, followed ''solely'' by one or more ASCII letters or digits (A-Z, a-z, 0-9)
which would exclude any extraneous characters.
And, yes, I know that one of the test cases (examples) shows this, but examples shouldn't be used as definitions. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 17:40, 31 August 2016 (UTC)
: Updated. --[[User:Smls|Smls]] ([[User talk:Smls|talk]]) 06:19, 1 September 2016 (UTC)
Another case I find useful is "libglfw.so.3.1" => "so", and always returning lowercase results. Just sayin [[User:Petelomax|Pete Lomax]] ([[User talk:Petelomax|talk]]) 12:18, 9 September 2016 (UTC)
In Unix and Unix-like environments
.desktop
is a hidden file or directory and not a file extension.
: Updated:--[[User:Garak|Garak]] ([[User talk:Garak|talk]]) 12:34, 21 December 2017 (UTC):
:: That's why the specification says "For the purposes of this task", and the task allows showing a built-in standard library function that behaves differently. --[[User:Smls|Smls]] ([[User talk:Smls|talk]]) 16:32, 21 December 2017 (UTC)
== Use Libraries not Footguns ==
Practicing programmers should strongly prefer to use existing filesystem APIs to extract file extensions.
Why?
1. Doing this correctly depends on the operating system (OS).
2. Such OS APIs exist for a reason! Use them!
3. Generally speaking, handling strings correctly is harder than many programmers realize. There are many gotchas in doing this correctly.
4. You need to be smart about encodings and locales.
Therefore, for the sake of being *responsible* about what information Rosetta Code provides, it should do the following:
A. Make it abundantly clear that ad-hoc solutions are *not* applicable for real-world usage.
B. Point readers to the relevant APIs in their languages, operating systems, and libraries.
--[[User:Krebsikl|Krebsikl]] ([[User talk:Krebsikl|talk]]) 15:27, 7 August 2023 (UTC)
: It would help if you could name even just one of them, and at least one example that c/would go horribly wrong. I was not aware of any suitable OS APIs for this, perhaps you meant PathCchFindExtension, but that is not capable of solving this task. I would agree that handling strings is much harder than it should be, and quite ridiculously so in most popular (/terrible) programming languages, and via most OS APIs. If some task on rc is not suitable for real-world use, then (like you just have) you need to start a debate on that task's discussion page, and (possibly with a limited few exceptions for complexity or security reasons) try and lick the task into something that '''is''' useful, since comparing programming languages (the whole purpose of this site) for completely unusable tasks is, well, all rather pointless. --[[User:Petelomax|Petelomax]] ([[User talk:Petelomax|talk]]) 15:48, 9 August 2023 (UTC)
| |||