Page 3 of 3 <123
Topic Options
#155304 - 06/01/19 02:12 PM Re: *not a bug*
Lonkero Administrator Offline
KiX Master Guru
*****

Registered: 01/06/05
Posts: 22294
Loc: Claremore, OK
Quote:


It is a work-around, but I don't think that it's a good long term solution to say 'using $var="VALUE" on the command line doesn't always work as you'd expect so you're better off parsing the line yourself'. Much better to fix '$var="VALUE"' so that it always works as expected.





again, you are not reading me.
Ruud can easily fix this inbuild if he skips using argv and starts using getCommandLine();
he doesn't have to do anyhing more but to add a strtok(); (or what the c-split was...)

when he gets to using the getCommandLine, he could also add the whole string in to the macro he is promising.
but lets not mistake that I ever said user should parse the commandline.
it was ruud and some other folks.
_________________________
!

download KiXnet

Top
#155305 - 06/01/19 02:24 PM Re: *not a bug*
Shawn Administrator Offline
Administrator
*****

Registered: 99/08/13
Posts: 8606
So if Ruud "fixes" this issue (i still maintain that nothing is broke) ... how many scripts you figure might break because of it ?
Top
#155306 - 06/01/19 02:48 PM Re: *not a bug*
Lonkero Administrator Offline
KiX Master Guru
*****

Registered: 01/06/05
Posts: 22294
Loc: Claremore, OK
none.
btw, searched for some time and found:
http://msdn.microsoft.com/library/en-us/...e_Arguments.asp

so, like I remembered, you can even disable the flawed argument parsing routines thus saving space.
didn't try though how this does affect the working ones.
_________________________
!

download KiXnet

Top
#155307 - 06/01/19 03:08 PM Re: *not a bug*
Richard H. Administrator Offline
Administrator
*****

Registered: 00/01/24
Posts: 4945
Loc: Leatherhead, Surrey, UK
Quote:

but lets not mistake that I ever said user should parse the commandline.
it was ruud and some other folks.



Ahhh. You said "instead of using the args parsed for you, parse them yourself from the raw commandline" and I misunderstood.

Quote:

how many scripts you figure might break because of it ?




Agree with Jooel - it shouldn't break anything, unless someone is relying on "\\" at the end of an argument being reduced to "\".

Top
#155308 - 06/01/19 03:29 PM Re: *not a bug*
Shawn Administrator Offline
Administrator
*****

Registered: 99/08/13
Posts: 8606
my two cents - I don't think Ruud should be changing the documented behavior of the Windows runtime library.
Top
#155309 - 06/01/19 08:02 PM Re: *not a bug*
iffy Offline
Starting to like KiXtart

Registered: 05/05/29
Posts: 149
Loc: The Netherlands
Well, personally I think the average KiX programmer could care less if it's documented behavior or not, or if the problem is in the programming language or the OS.

I think that the average KiX programmer wants simple consistent ways of working with KiX and not having to think and be aware of, to quote Richard, idiosyncratic and inconsistent environments.

I still vote for fixing the commandline parsing of KiX but if not please let's document this odd behaviour very clearly with one or more good examples.

Slightly offtopic rant follows...
I'm still curious to know of other specific examples where this issue if manifested. If you try dir "c:\config.sys\" for example it is not interpreted as dir "c:\config.sys", clearly MS 'fixed' the issue themselves. I spend hours every day doing system administration from the commandline, either with MS or 3th party tools in a variety of scripting languages but I've never in all these years come across this. I did learn to live with the annoying double quote thingy, the carot I don't see as an oddity, it just is the defacto escape character on the (nt) commandline.

Top
#155310 - 06/01/19 08:21 PM Re: *not a bug*
Shawn Administrator Offline
Administrator
*****

Registered: 99/08/13
Posts: 8606
Quote:


I still vote for fixing the commandline parsing of KiX but if not please let's document this odd behaviour very clearly with one or more good examples.





Can't argue with that, no way and I agree. Should be documented. I've gone through hell trying to sort this stuff out too. The big reason I'm suggesting (and this is my two cents) that it not be fixed is because you know how these "lets fix something at our end that is broke at their end" things go ... what happens is that they fix things at their end then your end breaks.

Top
#155311 - 06/01/19 09:50 PM Re: *not a bug*
Lonkero Administrator Offline
KiX Master Guru
*****

Registered: 01/06/05
Posts: 22294
Loc: Claremore, OK
eh?
whose end?
kixtart is single developer thing.
if he fixes it, there is no other end to screw it up.
_________________________
!

download KiXnet

Top
#155312 - 06/01/19 10:04 PM Re: *not a bug*
Shawn Administrator Offline
Administrator
*****

Registered: 99/08/13
Posts: 8606
So what are you suggesting ? That Kixtart use GetCommandLine() to get the raw command line, then parse it using new rules that aren't so odd ?
Top
#155313 - 06/01/19 10:16 PM Re: *not a bug*
Lonkero Administrator Offline
KiX Master Guru
*****

Registered: 01/06/05
Posts: 22294
Loc: Claremore, OK
new rules?
parse it with the old rules.
just like the manual dictates.
that's not so hard.
see wkix32.exe, it already does work properly.
old rules, fixed functioning.
_________________________
!

download KiXnet

Top
#155314 - 06/01/19 10:22 PM Re: *not a bug*
Les Offline
KiX Master
*****

Registered: 01/06/11
Posts: 12734
Loc: fortfrances.on.ca
Leave KiX32.exe the way it is and use WKiX32.exe for the new school way and nothing breaks.
Why can't you just let it go and get on with your life?
_________________________
Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.

Top
#155315 - 06/01/19 10:34 PM Re: *not a bug*
Lonkero Administrator Offline
KiX Master Guru
*****

Registered: 01/06/05
Posts: 22294
Loc: Claremore, OK
new school?
again, the syntax of kixtart commandline has been same for looooong time.
some switches have been added but otherwise, it has remained the same.

so, what does "new school" mean?
are you saying that if someone finds a bug long time after software is published, it should not be fixed in future versions?
_________________________
!

download KiXnet

Top
#155316 - 06/01/19 10:41 PM Re: *not a bug*
Shawn Administrator Offline
Administrator
*****

Registered: 99/08/13
Posts: 8606
I'm taking your advise Les and letting it go. Suggest you do same.
Top
#155317 - 06/01/20 02:19 AM Re: *not a bug*
Chris S. Offline
MM club member
*****

Registered: 02/03/18
Posts: 2368
Loc: Earth
I don't know, I kinda have to take sides with Lonk on this one. If it behaves one way with KiX32.exe it should behave exactly the same way with WKiX32.exe. Otherwise you'll have to have two scripts (one for WKiX and one for KiX) to properly parse the command line.
Top
#155318 - 06/01/20 03:16 PM Re: *not a bug*
Les Offline
KiX Master
*****

Registered: 01/06/11
Posts: 12734
Loc: fortfrances.on.ca
I have only one word to toss in here and then will take my own advice as suggested by Shawn.

LEGACY
_________________________
Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.

Top
#155319 - 06/04/17 12:07 PM Re: *not a bug*
Ruud van Velsen Offline
Developer
*****

Registered: 99/05/06
Posts: 357
Loc: Amsterdam, The Netherlands
RC1 will have the new @COMMANDLINE macro. I hope that resolves most issues without breaking any of the existing scripts.

Ruud

Top
Page 3 of 3 <123


Moderator:  ShaneEP, Arend_, Jochen, Radimus, Glenn Barnas, Allen, Mart 
Hop to:
Shout Box

Who's Online
0 registered and 113 anonymous users online.
Newest Members
schnuggel, h315060, johnnyutah, pmk31, ArserHsieh
17412 Registered Users

Generated in 0.11 seconds in which 0.066 seconds were spent on a total of 13 queries. Zlib compression enabled.