Empty symlinks and full POSIX compliance
Empty symlinks and full POSIX compliance
Posted May 27, 2013 18:40 UTC (Mon) by pr1268 (guest, #24648)Parent article: Empty symlinks and full POSIX compliance
...the [POSIX] standard was updated to allow either the Solaris or the BSD behavior.
What a washout. POSIX should choose one are the other and stick with it.
...it was a standard created to document what is actually in use to limit/prevent fragmentation between implementations. -dlang
By not choosing one specific behavior of empty symlinks, POSIX is only adding to the fragmentation. Sigh...
Historical side note bearing similarity: In 1960, the Federal Communications Commission (FCC) was tasked with choosing a single stereophonic FM broadcast standard from among 14 submissions (from a number of different companies). They chose one based on the technical merits known at the time, and upset the other companies which had submitted a proposal. Oh well. Fast forward to 1980, and again, the FCC was tasked with choosing a single AM stereo1 specification (from four submissions, each from a different company). Instead, the FCC chose not to choose one, deciding that any of the four standards could be used2. I believe this caused more ire than the FM row twenty years prior.
1 I can't argue the need for AM stereo - it's a low-fidelity medium not well-suited for stereophonic content anyway.
2 If I understand 47 CFR §73.128 correctly, the FCC has since regulated stereo AM to a single specification. I think it's a moot point, anyway; when's the last time anyone saw consumer audio hardware proudly sporting AM stereo capability?
