Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

One of the Focuses of V17 Beta Testing Should Be Command Line Parsing

Dec
236
2
In one of my posts, Rex posted the following:

RCONN: "About 98% of the command line parsing was changed between v16 and v17. A lot of inconsistencies were removed, previously uncaught errors are now caught, and everything is faster (and smaller)."

So far I have had two issues that were related to command line parsing, IFTP and JABBER. With 98% of the command line parsing changed. I would suggest testing all your aliases and batch files to make sure commands are parse as you expect them to be.
 
Here's something that doesn't work the way it did in v16. First, from v16:
12 C:\btm ver
TCC 16.03.55 Windows 7 [Version 6.1.7600]
0 C:\btm type clip:
72053
72061
72062
72062
0 C:\btm for z in (@clip:) echo %z
72053
72061
72062
72062

Next, from v17:
11 C:\btm ver
TCC 17.00.42 Windows 7 [Version 6.1.7601]
0 C:\btm type clip:
72053
75060
72062
72063
0 C:\btm for z in (@clip:) echo %z
@clip
:

Peter
 
Back
Top
[FOX] Ultimate Translator
Translate