-----BEGIN PGP SIGNED MESSAGE-----
Kwong Goh wrote:
| I am using optionparser to take in arguement. However, it seems like the
| option parser does not accept “&” “|” “<” “>” as the arguement when they
| are entered from the command line.
| For example, I use opts.on("-d option"), when I enter -d 1&2 in the
| command line, it will only accept 1 in this case.
| May I know what is the reason for this and how to solve this problem?
Try to use a ‘dir > text.txt’, or ‘ls > text.txt’, or ‘dmesg | grep a’
on the command line.
The symbols OptionPArse doesn’t accept are reserved by the OS.
(| is the pipe in *NIX, && allows comamnd chaining in Windows and *NIX,
< and > are redirectors, which allow the use of a file as input to a
command, or direct the output of a command to a file, respectively.
There is no way I am aware of to circumvent these, except “Stop using
them”. Maybe others know more.
Make sure all variables are initialised before use.
~ - The Elements of Programming Style (Kernighan & Plaugher)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----