Or look at the whole succession of security holes in shell scripts and even other languages caused by control characters in filenames. This frustrates efforts to treat them as Unicode strings and cleanly allow international characters. Currently on a Unix-like system you cannot assume anything more about filenames than that they're a string of bytes. Look at the recent Python version that got tripped up by filenames that are not valid UTF-8. ![]() ![]() If using a single character for end-of-line was the best design decision in UNIX, then allowing any character sequence in filenames (while at the same time including a shell and scripting environment that's easily tripped up by them) was the worst.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |