| |||||||||||||
Control characters in file namesControl characters in file namesPosted Nov 29, 2010 14:40 UTC (Mon) by nix (subscriber, #2304)In reply to: Control characters in file names by michaeljt Parent article: Ghosts of Unix past, part 4: High-maintenance designs
Handling directory separation at a higher level would be a classic That Hideous Name nightmare, converting paths from a simple string to a complex structure involving N components with associated lengths, which would *still* have to be somehow converted to a string a lot of the time: and if you can do that, you need a quoting mechanism to make it unambiguous, and if you have *that*, you could use the same quoting mechanism at input time, and still retain the /.
The current situation with /-and-no-quoting-characters is simplest of all, and eliminates the numerous attacks we have seen on SQL and other languages involving incorrectly processed quoting characters.
(Log in to post comments)
Control characters in file names Posted Dec 2, 2010 17:27 UTC (Thu) by Ross (subscriber, #4065) [Link]
Thank you for the sanity :)
Yes, having to concoct paths with some helper function in some nasty encoding would not be an improvement. If people think it's too hard for scripts to handle spaces -- wait until filenames can have slashes in them too!
|
|||||||||||||