Done Add an option to control command line parsing

Dec 22, 2008
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! :-)
 

rconn

Administrator
Staff member
May 14, 2008
12,316
148
who_are_you wrote:

> 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.

This is WAD, for compatibility with CMD.EXE. I think it would be a bad
idea to make this configurable, as it would result in more more
incompatibilities with existing batch files written for CMD.

Rex Conn
JP Software
 
Dec 22, 2008
7
0
who_are_you wrote:


> char to seperate parameters. This behavior is not expected in most
> cases.

This is WAD, for compatibility with CMD.EXE. I think it would be a bad
idea to make this configurable, as it would result in more more
incompatibilities with existing batch files written for CMD.

Rex Conn
JP Software

Is it very very important to make TCC compatible with CMD.exe? The reasons that I like to use 4NT and TCC/LE never include the compatibility with stupid CMD.exe. The problem here is that TCC and TCC/LE is not compatible with previous 4NT. I think many users may have the same feature request:-)

By the way, I always set my TCC/LE to use settings compatible with 4DOS. In this way, most of my very early 4DOS scripts can even run with TCC/LE. So I think many users will be happy to see compatibility with previous 4NT or 4DOS:-)
 
Jun 3, 2008
115
1
Temecula, CA
>Is it very very important to make TCC compatible with CMD.exe? The
reasons

>that I like to use 4NT and TCC/LE never include the compatibility with
>stupid CMD.exe. The problem here is that TCC and TCC/LE is not
compatible

>with previous 4NT. I think many users may have the same feature
request:-)

>
>By the way, I always set my TCC/LE to use settings compatible with
4DOS. In

>this way, most of my very early 4DOS scripts can even run with TCC/LE.
So I

>think many users will be happy to see compatibility with previous 4NT
or


Yes, it is very very important to make TCC compatible with CMD.exe.
First, there is the consideration of TCC/LE, which Rex provides for
free. It has to be 100% compatible (or at least as much as feasible)
with CMD.exe. It's intended to be a teaser to get the user into the TCC
world and make them want to upgrade (for a cost) to full TC.

More importantly, though, there are a lot of users who write their
scripts in TC, but also need them to work for other users who don't have
TC and run them in CMD. This is especially true of the installed base.
Eliminating the compatibility requirement breaks all of them. Rex would
lose a lot of customers if he didn't maintain compatibility wherever
possible.
 

samintz

Scott Mintz
May 20, 2008
1,488
15
Solon, OH, USA
Personally, I find that it's the scripts written for public consumption
that come packaged with certain tools for example that require the CMD
compatibility. I always create my TCC scripts with a BTM extension so
that I *know* they won't run in CMD.

-Scott

"JP Software Forums" <neil@jpsoft.com> wrote on 01/07/2009 11:45:52 AM:


> Yes, it is very very important to make TCC compatible with CMD.exe.
> First, there is the consideration of TCC/LE, which Rex provides for
> free. It has to be 100% compatible (or at least as much as feasible)
> with CMD.exe. It's intended to be a teaser to get the user into the TCC
> world and make them want to upgrade (for a cost) to full TC.
>
> More importantly, though, there are a lot of users who write their
> scripts in TC, but also need them to work for other users who don't have
> TC and run them in CMD. This is especially true of the installed base.
> Eliminating the compatibility requirement breaks all of them. Rex would
> lose a lot of customers if he didn't maintain compatibility wherever
> possible.
>
>
>
>
 
May 20, 2008
3,515
4
Elkridge, MD, USA
samintz wrote:
| Personally, I find that it's the scripts written for public
| consumption
| that come packaged with certain tools for example that require the CMD
| compatibility. I always create my TCC scripts with a BTM extension so
| that I *know* they won't run in CMD.

IMHO the default for batch files with .CMD extension ought to be to emulate
the latest version of CMD as perfectly as possible, and for .BTM extension
to be backward compatible to earlier versions of JPsoft command processors,
with a method to switch between the modes for .BTM extension. Losing
backward compatibility alienates long-time JPsoft customers, and results in
many support requests, when "upgrading" kills long working batch programs,
esp. since there is no easy path to go back to the earlier versions after
using the MS installers.
--
Steve
 

rconn

Administrator
Staff member
May 14, 2008
12,316
148
who_are_you wrote:


> Is it very very important to make TCC compatible with
> CMD.exe?

Yes, it is very very important -- just witness the screams of outrage on
the support forum if I change something in TCC that introduces an
incompatibility with CMD.

The whole purpose of TCC is to be a superset of CMD. An incompatible
superset doesn't have much appeal!

Rex Conn
JP Software
 
Jun 3, 2008
27
0
On Wed, 07 Jan 2009 10:46:22 -0600, "JP Software Forums"
<neil@jpsoft.com>,MickeyF <> wrote Re RE:
[Suggestions-t-734] Re: Add an option to control command line parsing:


>Yes, it is very very important to make TCC compatible with CMD.exe.

I agree.
--
At first they laugh at you, then they ignore you, then they fight you, then you win.
 
Similar threads
Thread starter Title Forum Replies Date
R Option to add tcc to Bash profile Suggestions 1
D Done Suggestion: Add VIEW option to open in same position as current window Suggestions 0
D Done BDEBUGGER: add cmdline option to set a breakpoint at a given line Suggestions 0
R Declined Install option: Add File Explorer Run As Adminstrator option Suggestions 14
Charles Dye Done @SNAPSHOT: Add option to capture the entire virtual screen Suggestions 0
rps Declined ECHO -- Add spacing option Suggestions 2
D Done Add VIEW option to open in same position as current window Suggestions 0
rconn Add option to run programs Elevated from toolbar buttons Suggestions 0
G Declined Add option to turn on file name case sensitivity Suggestions 6
S Declined Add /W(ipe) option to several commands Suggestions 17
E Declined Add option to use SFN for ComSpec variable Suggestions 8
Joe Caverly Done Add ability to DEL Stream from SYMLINK Suggestions 2
Joe Caverly Add VHD to @drivetype Suggestions 1
R Add Custom Message to commands Suggestions 2
mfarah Declined Implement an "Add TCC to the task bar" in the TCMD installer. Suggestions 2
C Declined Add switch to MOVE to not make empty destination folders. (COPY's /F) Suggestions 4
M Add "ReleaseID" (aka version or build) to ver output Suggestions 2
R Declined In setup, add back/refresh buttons. Suggestions 1
D Done TCEdit and BDEBUGGER: add cmdline switch to jump to given line Suggestions 2
R Done Add "Evaluate Expression" to Right-Click Context Menu in Batch Debugger Suggestions 3
S Add support for Git auto-completion Suggestions 0
R Declined wish-list: add a command to copy a file to clipboard. Suggestions 17
Dmitry L. Kobyakov Done Add the possibility to comment the ENDIFF Suggestions 11
Charles Dye Declined Windows functions and command: Add syntax to specify HWND directly Suggestions 0
R Done Add Libraries and Multi-line In-Memory functions to Features List on Website Suggestions 1
R Done Add to Pause Help text re indenting the prompt Suggestions 0
C Done Add ability for inline image files for sendmail or similar Suggestions 2
WinLanEm Add commands and functions Suggestions 11
rps Declined Add auto-load directives to tcmd.ini Suggestions 3
fromano Declined Add library functions to shralias saving feature Suggestions 12
Joe Caverly Add a "Snippet" Menu to CMDebug and TCC Debugger Suggestions 0
D Done Add the ability to control syntax coloring via an environment variable or some other way Suggestions 3
Joe Caverly Add example .BTM code to TCC Debugger and CMDebug Suggestions 1
Alpengreis Done Add "Slow copy" (/WAIT) parameter to SYNC command Suggestions 1
Charles Dye Done MOUNTISO: Add support for VHD / VHDX files Suggestions 5
A Declined Take Command/Debugger as a Visual Studio 2017 add-in/extension Suggestions 4
rps Declined Add optional parameters to @search Suggestions 4
rps Done Add PDIR switches Suggestions 1
vefatica Done Add log2 to @EVAL Suggestions 3
rps Done Add exclusion ranges to @files Suggestions 0
R Done Add a .btm LIBRARY system Suggestions 12
N Done Add display options to new HASH function Suggestions 1
rconn Add a parameter to dir command to handle zip files as folders Suggestions 1
rconn add support for batch file projects Suggestions 0
rconn Add support for backpipes Suggestions 0
rconn In the Help tab let the user add links either to files or web pages, with an icon & label. Suggestions 0
W Done Add colorize to tree command? Suggestions 0
Phileosophos Done Please add options for scrollback buffer searching Suggestions 24
nickles Done Add a "Mark all threads read" button Suggestions 3
B Done Add New INI Directive To Specify WIPE Default Pass Count Suggestions 0

Similar threads