#155307 - 2006-01-19 03:08 PM
Re: *not a bug*
|
Richard H.
Administrator
Registered: 2000-01-24
Posts: 4946
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
|
|
|
|
#155309 - 2006-01-19 08:02 PM
Re: *not a bug*
|
iffy
Starting to like KiXtart
Registered: 2005-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 - 2006-01-19 08:21 PM
Re: *not a bug*
|
Shawn
Administrator
Registered: 1999-08-13
Posts: 8611
|
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
|
|
|
|
Moderator: ShaneEP, Arend_, Jochen, Radimus, Glenn Barnas, Allen, Ruud van Velsen, Mart
|
0 registered
and 259 anonymous users online.
|
|
|