Hi!
28-Ноя-2006 08:59 [EMAIL PROTECTED] (Roberto Mariottini)
wrote to freedos-user@lists.sourceforge.net:
RM> IIRC when command.com parses the command line the first non-filename
RM> character is used to separate the command name from the command line
RM> (the space character is one of them),
Unfortunately, this is not complete true. For example, compare "echo.",
"echo.exe" and "mycmd.exe" commands.
RM> so the character = after PATH will
RM> break the command from the command line and will be put on the command
RM> line. The PATH command ignores an = at the start of the path list so you
RM> get the "PATH=something" syntax working. Other characters get the same
RM> result (for example "PATH,something") and other are put in front of the
RM> path list (like "PATH;something").
On the other side, I know programs, which use "=" as valid character in
its command line. So, if add support for "var=val", then this breaks
programs, which expect "=" as first character in command line. Really first
character - if you add space before "=" ("prog =..."), then this adds space
also into command line (in PSP).
RM> Supporting the generic VAR=VALUE assignment (meaning SET VAR=VALUE)
RM> could break old programs that use the = character for special meaning on
RM> the command line (such as old linkers and librarian utilities).
Yes.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
