OSDev.org

yes in mine too
but what about <'s most people dont use it because dos and windows down allow it in filenames but couldn't this cause some sort of problem and my idea is like this(with some rethought)
my_cmd<arg1,*arg2>another_cmd_yay<arg1,*arg2>
and the arg2's are variables as shown by the *
and it would execute the command and send it the argument in the form of the trailing> replaced with a null and the < turned into a null to seperate the command and argument but it still be in the same variable

yes and unreadible characters shouldnt be allowed imho

and well actually following that format "'s would be allowed in filenames not sure if anyone would use them though

Da_Maestro wrote:In *NIX you can even put unreadable characters in filenames, characters such as carriage returns and bells. Makes it really confusing when the names in your drive get corrupted

you could do that in DOS also -- it was commonly recommended as a security feature, since you would have to know exactly how the filename was written to use it -- ex. rename format -> format with a special character (like 255) at the end -- someone looking for trouble would never know why they couldn't use the file since it was listed