- Dec
- 7
- 0
Recently I find a problem on command line parsing involving "=".
For example, if we have the following script called "test.btm":
================================
echo %1;%2;%3;%4
================================
then running "test a=1 b=2" will display "a;1;b;2".
However, in earlier version of 4NT, the above script will display "a=1;b=2;;".
So the tests above show that current TCC/LE will regard "=" as one special char to seperate parameters. This behavior is not expected in most cases. Hence, I suggest JPSoft to add one option to SETDOS command so as to control whether to use "=" to parameter delimiter.
I am expecting next release of TCC/LE with new functions! :-)
For example, if we have the following script called "test.btm":
================================
echo %1;%2;%3;%4
================================
then running "test a=1 b=2" will display "a;1;b;2".
However, in earlier version of 4NT, the above script will display "a=1;b=2;;".
So the tests above show that current TCC/LE will regard "=" as one special char to seperate parameters. This behavior is not expected in most cases. Hence, I suggest JPSoft to add one option to SETDOS command so as to control whether to use "=" to parameter delimiter.
I am expecting next release of TCC/LE with new functions! :-)