4 ms·
You wouldn't like Plan 9 then; it wisely took the decision to forbid spaces (U+20) in file names at the kernel level.
by ralph 14y ago
You wouldn't like Plan 9 then; it wisely took the decision to forbid spaces (U+20) in file names at the kernel level.
- sturadnidge 14y agoI don't care about it - I'm saying the people who use operating systems (as opposed to the people who administer them) do.
- 4ad 14y agoJust a small correction. While nobody uses spaces in file names in Plan 9, and at least in Inferno #U changes spaces to something else, spaces are not forbidden in the kernel since March 23th, 1999: http://swtch.com/cgi-bin/plan9history.cgi?f=1999/0323/port/chan.c;v=diff;e=1 http://swtch.com/cgi-bin/plan9history.cgi?f=1999/0323/port/c...
- ralph 14y agoThanks, I think you've corrected me on this before and I haven't learned! My Plan 9 comes from before this switch.
- dagw 14y agoIt has nothing to do with liking or not liking spaces per se, but simply that you should support the features that the operating system allows. Look I hate spaces (and non-ASCII characters for that matter) in files names as much as the next programmer who's ever had his code fail due to them, but if I'm writing for a platform that supports them, then I try my best to deal with them, and tread any failure in handling them as a bug that should be fixed.