Is it a Good Idea?: $CmdLineRaw as a Macro

[TheDcoder]

Hello! I am back with another IIAGI? (Is it a Good Idea?)

 

I think $CmdLineRaw is more like a macro than a "special" variable (which cannot be changed)... So making ti @CmdLineRaw would make more sense and there will 1 less exception to variables , I know that you were wondering about the $CmdLine "special" array... I didn't forgot it, but I don't think a macro can be a array, so I just ignored it... Maybe removing the $CmdLine and changing $CmdLineRaw to @CmdLine would be nice if you ask me .

 

Think before choosing! TD

 

P.S Feel free to disagree with me, I want hear your opinion as well .

[orbs]

changing anything in $CmdLine[] & $CmdLineRaw now, will give a whole new meaning to the concept of maintaining backward compatibility 

in practice, it is true that AutoIt is somewhat lacking in it's way of handling command line arguments; that's why several users have come up with their own methods and UDF. this is one such example:

[MachinistProgrammer]

I think it would be better to have both @CmdLine and @CmdLineRaw.

A macro better expresses the behavior of $cmdline and by keeping both.

But this would also make breaking changes for little gain.

[TheDcoder]

@orbs Yeah, but the people who want those feature can use older version (like @TheSaint)

@MachinistProgrammer Hmm... a macro array? , While I agree that it will create breaking changes, AutoIt Coder can easily fix the issue by using a simple Replace operation

 

TD

[JohnOne]

A macro by definition is a quick way of getting some run-time system information which may differ from machine to machine. the command line parameters are not like that they are absolute and provided by the user.

I initially cannot see a reason to have it look like a macro.

[TheDcoder]

@JohnOne What about @MIN @SEC etc?

 

I need to go, I will be back later, TD

[JohnOne]

At run-time, you don't know what @sec is, and it changes, well, every second. while command line is still absolute and remains so for the lifetime of your script.

EDIT:

I might be similar to doing this...

Global Const $GCONST = 99.9

$value = 100 / _GetGlobalConst()

Func _GetGlobalConst()
    Return $GCONST
EndFunc

 

Edited December 15, 2015 by JohnOne

[TheDcoder]

@JohnOne How do you explain @CRLF then? They remain the same the whole life . This Quote is taken from the help file:

...macros are generally used to provide easy access to system information...

As you can see that macros "generally" provide easy access to system... There is no rule that the should only provide "that", viz. the birth of @CRLF

[JohnOne]

A Line Feed or Carriage Return can be different from machine to machine.

[TheDcoder]

@JohnOne R-R-Really?

[JohnOne]

Yes, that is why there is a macro for it.

[TheDcoder]

What about @WorkingDir? Its set by the user too... I guess...

[JohnOne]

Every AutoIt macro is there to save you from writing a bunch of lines yourself to get the correct information, you can list them all one by one if you wish to but it wont change it.

With $CommandLineRaw, you'd be replacing $ with @ and probably making some internal call which is not needed.

I've tried, but still cannot see a single valid reason to have it.

[TheDcoder]

... Yet, I lose again

 

Good job, J1

[JohnOne]

You never lose when you learn something.

[TheDcoder]

True

[TheSaint]

Except a little naivety perhaps .... we all try to lose that.

[Jos]

A Line Feed or Carriage Return can be different from machine to machine.

Don't think this is 100% correct. I would have said that a "newline" is sometime CRLF and sometimes either LF or CR.
 

On this topic in general: it feels like some people have way too much time on their hands to come up with these kind of proposals and have this lengthy discussion about it.
These design decision where made a long time ago and honestly fail to see the benefit of any change other than when the goal is to confuse people.

.Jos

[TheDcoder]

some people have way too much time on their hands to come up with these kind of proposals and have this lengthy discussion about it.

[JohnOne]

Don't think this is 100% correct. I would have said that a "newline" is sometime CRLF and sometimes either LF or CR.

Indeed, I mis-remembered.