global variable or function?

[BrewManNH]

You can't put values into a variable the way you're looking to do with a Static variable, so you need to do it in more than one line, it's as simple as that. Just because you are trying to make your code shorter, and probably a lot harder to read and follow, doesn't mean you're going to be able to achieve that.

[Guest]

You can't put values into a variable the way you're looking to do with a Static variable, so you need to do it in more than one line, it's as simple as that. Just because you are trying to make your code shorter, and probably a lot harder to read and follow, doesn't mean you're going to be able to achieve that.

 

Now you understood my question.

Ok, I will live with it. It can only lead to more lines but if there is no way to shorten it so no matter.

 

I think it would be good if in the next versions of Autoit, will be added to the syntax something which is considered as @CRLF.

Just like _ is considered as "Continue the line (While you can write one line as few lines..), Then there is a need for something

that is translated to @CRLF During the Compile time.

So that way I can write:

$var1 = 1 [Key] $var2 = 2 [Key] $var3 = 3

(It is necessary to decide what [Key] will be choose for this purpose)

And the compiler will translate it to this:

$var1 = 1
$var2 = 2
$var3 = 3

 

I hope you get the point. Hard for me to explain in English

Edited January 20, 2015 by Guest

[Melba23]

gil900,

Why do you have this burning desire to reduce the number of lines in your script to an absolute minimum? What do a few more lines matter? The main thing is to keep the code readable so that you can return to it after a while and still understand what on earth is going on.

M23

[guinness]

I agree with Melba23. A nice addition to AutoIt might be a verbatim string literal, in which a new line sequence can be achieved by just hitting enter in the editor and not having to use @CRLF or such-like. I won't be adding it to trac though.

[Guest]

gil900,

Why do you have this burning desire to reduce the number of lines in your script to an absolute minimum? What do a few more lines matter? The main thing is to keep the code readable so that you can return to it after a while and still understand what on earth is going on.

M23

 

 

For me there is no difference between $var1 = 1 [Key] $var2 = 2 [Key] $var3 = 3 .

Suppose that [Key] is | then it looks easy to read:

$var1 = 1 | $var2 = 2 | $var3 = 3 | $var4 = 2 | _

$var5 = 13 | $var6 = 6 .........

EDIT: Fixed example ^

If it was with a lot of variables then definitely it was more comfortable to read the script because it would save a you a space to read more easily the rest of the code.

 

That's how I think.

I suggests considering developing this feature. Not everyone will have to use it ..

Anyone will do what is comfortable for him

Edited January 20, 2015 by Guest

[guinness]

You could create this yourself in a pre-processor if you feel it's of worth, though I can see if only causing more headaches or at least not be used. BY the way, AutoIt doesn't get compiled in the traditional sense, the "compiler" just adds the script as a resource to the interpreter, which is then read when the executable is run. Yes, the "compiled" executable is just the interpreter.

[Guest]

You could create this yourself in a pre-processor if you feel it's of worth, though I can see if only causing more headaches or at least not be used. BY the way, AutoIt doesn't get compiled in the traditional sense, the "compiler" just adds the script as a resource to the interpreter, which is then read when the executable is run. Yes, the "compiled" executable is just the interpreter.

 

You could create this yourself in a pre-processor if you feel it's of worth, though I can see if only causing more headaches or at least not be used.

Yes, I know. But if I do that then a nearly nobody will use it except me - not worth it.

 

AutoIt doesn't get compiled in the traditional sense, the "compiler" just adds the script as a resource to the interpreter, which is then read when the executable is run. Yes, the "compiled" executable is just the interpreter.

I know. Just to write in English, I save words.

I know that the word "compile" is not the most appropriate in this case but I do not know another word

[czardas]

A good place to use a static variable would be when you need to run a long process to assign a value to the variable. Here's a mock illustration of this type of use:

;

#include <MsgBoxConstants.au3>

For $i = 1 To 3
    ConsoleWrite(ParcelDelivery() & " hours delivery" & @LF)
Next

Func ParcelDelivery()
    Static $ParcelPost = LongProcess() ; This line of code only runs once, no mater how many times you call the function.
    $ParcelPost += 24 ; The current value of a static variable is kept in memory.
    Return $ParcelPost
EndFunc

Func LongProcess()
    Return (MsgBox($MB_RETRYCANCEL, "Long Process Simulator", "This process may take for ever!") = 4) ? LongProcess() : 0
EndFunc

Edited January 20, 2015 by czardas

[Guest]

There are many uses for it.
I thought about this usage

SomeFunc()
SomeFunc()
SomeFunc()
Func SomeFunc()
    Local Static $IsFRunned ; Is the function was not runned before?
    If Not $IsFRunned Then
        ConsoleWrite('This is the first time that the function is running' &" (Line "&@ScriptLineNumber&")"&@CRLF)
        $IsFRunned = 1 ; Whe have to update it to 1 in this case so it will not happen again
    Else
        ConsoleWrite('This is NOT the first time that the function is running' &" (Line "&@ScriptLineNumber&")"&@CRLF)
    EndIf
    
    ; ... Some code that use $IsFRunned ...
EndFunc

Edited January 20, 2015 by Guest

[czardas]

Yes that's another example of usage.

Edited January 20, 2015 by czardas

[guinness]

There are many uses for it.

I thought about this usage

SomeFunc()
SomeFunc()
SomeFunc()
Func SomeFunc()
    Local Static $IsFRunned ; Is the function was not runned before?
    If Not $IsFRunned Then
        ConsoleWrite('This is the first time that the function is running' &" (Line "&@ScriptLineNumber&")"&@CRLF)
        $IsFRunned = 1 ; Whe have to update it to 1 in this case so it will not happen again
    Else
        ConsoleWrite('This is NOT the first time that the function is running' &" (Line "&@ScriptLineNumber&")"&@CRLF)
    EndIf
    
    ; ... Some code that use $IsFRunned ...
EndFunc

Maybe use True or False and take full advantage of the language. Another thing $bHasFuncRun, denotes that the variable datatype is boolean, just as $iAge tells that it's an integer. This greatly improves code readability and reduces errors where a string is "accidentally" assigned to a variable that should be a number.

Unfortunately AutoIt isn't strongly typed, so we (the coders) need to add some method to ensure that we don't inadvertently mess up along the way, despite AutoIt being too forgiving. Now if there was a type checking script, then we could adopt a similar approach to how TypeScript ensure variables in JavaScript are strongly typed with zero overhead.

 

Local $age: Int = 21
Local $name: String = "guinness"
$name = 100 ; This would display an error, and thus wouldn't be able to "compile" the script.

[TheSaint]

TheSaint,

 

This demonstrates using the latest version of AutoIt, what we have been talking about. You might want a Global variable when you have a filehandle open, but then people could argue even this can be done without a global variable, which they would be right in saying.

 

expandcollapse popup

#include <File.au3>
#include <StringConstants.au3>

Global $g_sSomeBigString = "" ; As this is only used in the Example function, why is it declared here?
Global $g_hFile = FileOpen(_TempFile(), BitOR($FO_READ, $FO_OVERWRITE)) ; This is okay, as it's referenced in more than one place.

OnAutoItExitRegister(OnClose) ; Register a function to call on AutoIt exit.

Example()
Write()
ReadAndReplace()

Func Example()
    ; $g_sSomeBigString should be called $sSomeBigString and declared using Local.
    For $i = 0 To 100
        $g_sSomeBigString &= String($i)
    Next
    ConsoleWrite($g_sSomeBigString & @CRLF) ; Since this is only used here.
    Return Null ; Like void.
EndFunc   ;==>Example

Func OnClose()
    FileClose($g_hFile) ; Tidy resources on exit.
    Return Null ; Like void.
EndFunc   ;==>OnClose

Func ReadAndReplace()
    FileSetPos($g_hFile, 0, $FILE_BEGIN)
    Local $sFileRead = FileRead($g_hFile) ; Assign to a local variable.
    FileSetPos($g_hFile, 0, $FILE_BEGIN)

    $sFileRead = StringReplace($sFileRead, "1", "", 0, $STR_NOCASESENSE) ; Manipulate the data in the variable.
    ConsoleWrite($sFileRead & @CRLF)
    $sFileRead = "" ; Pointless as this will be destroyed once this function is returned from.
    Return Null ; Like void.
EndFunc   ;==>ReadAndReplace

Func Write()
    FileSetPos($g_hFile, 0, $FILE_BEGIN)
    For $i = 0 To 1000
        FileWrite($g_hFile, $i & @CRLF)
    Next
    FileSetPos($g_hFile, 0, $FILE_BEGIN)
EndFunc   ;==>Write

Does anyone have a valid example?

 

Oops, just noticed this buried in amongst all the other posts.

Thanks, food for thought.

Pretty straightforward, but very different from my simplistic approach, where I keep Declaration and Assignments separate.

[guinness]

where I keep Declaration and Assignments separate.

I never understand why people do that, especially in a scripting language where the script is interpreted line by line.

[TheSaint]

I guess it is a bit like how some eat their meat and veg.

Many eat them separately.

I don't tend to, unless the meat is exceptional and I really want to savor it on its own.

Still, I'm not a big fan of eating many cooked veggies on their own, without some meat in the mix.

Really though, it's a deliberate approach I favor.

I like to read things line by line in a simple manner.

This means that I often deliberately avoid nesting statements or commands.

Just an aid to troubleshooting I guess ... and easier to borrow code from, with less chance of introducing a bug (i.e. you forgot to edit .... I do a lot of copy and paste to save time).

The mystery of different minds working in different ways to achieve essentially the same end goal.

P.S. I guess for me, it is also tied in with issues like, knowing I would be better served by a function, instead of duplicating code, but I'm in a hurry, or more often than not, I have so much in my head, I don't want to risk forgetting something (possibly a nifty idea or three), while being diverted coding said function. Sometimes I go back later and create that function, especially during an update (if I'm reminded or notice or essentially need to re-use the code for a new bit).

Edited January 21, 2015 by TheSaint

[czardas]

I never understand why people do that, especially in a scripting language where the script is interpreted line by line.

 

It sometimes makes sense to declare several related variables (which may or may not be used) in one part of the script and assign values as and when needed. With a complicated script, this approach may simplify things. I would not do this with all variables - normally they would have to be family members.

Edited January 21, 2015 by czardas

[guinness]

Well in C# it's said (in the community) that it's pointless to declare a variable with the default value e.g. object objectVar = null, as you're repeating what the compiler does behind the scenes. I also get it in regards to loops in AutoIt (doesn't apply to Java or C#) where for execution purposes it's best to declare outside a tight loop. Otherwise, I see it as good coding practice to declare and intialise, generally speaking.

[czardas]

Also, you don't always know what the value will be and getting the value may involve a long process. Again I don't think there is a black and white answer to this. I always think about memory usage: large array - long process - may not be needed ==> DO NOT INITIALIZE.

Edited January 21, 2015 by czardas

[guinness]

Of course not. I realise this "rule" can't be followed 100% of the time, but a good 90% of the scripts I write can.

[czardas]

It's good to hear about differences in approach (and between different languages) guinness. It often reveals new ideas.

Edited January 21, 2015 by czardas

[Guest]

I never understand why people do that, especially in a scripting language where the script is interpreted line by line.

 

You never understand?

It seems that you understand here:

 

If one of the variables is large array then it can take memory..

So it is better to declare this kind of variable only when necessary.

But I changed my mind.

I can declare all global variables at the top of the script without always having to assign them any value (like a large array).

And assign to them the value only when it first needed.

This should be a better way

 

 

 

You:

Yes, correct.

 

 

Or I did not understand exactly what you mean.

It's a little confusing me

Edited January 21, 2015 by Guest