-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Terry Reedy wrote: > Is NUL \0 allowed in POSIX file names? If not, could that be used as an > escape char. If it is not legal, then custom translated strings that > escape in the wild would raise a red flag as soon as something else > tried to use them. Per David Wheeler's excellent "Fixing Linux/Unix/POSIX Filenames"[1]: Traditionally, Unix/Linux/POSIX filenames can be almost any sequence of bytes, and their meaning is unassigned. The only real rules are that “/” is always the directory separator, and that filenames can’t contain byte 0 (because this is the terminator). [1] http://www.dwheeler.com/essays/fixing-unix-linux-filenames.html Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver at palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ9KHg+gerLs4ltQ4RAs0HAKCiAOxmB8oBJRIoOIK+OK2LryUN6ACgp64k fzGUNScJwcdzzod3N+5JhOE= =Cw4m -----END PGP SIGNATURE-----
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4