Static & Global

[DXRW4E]

Is possible (when Au3Check load a file, take all the names of the functions in that file, and then see if there are Gobal Static, and get to know them only in those functions that file) or to add a (Optional) directive or something like that, in order to indicate to Au3Check the names of the functions where Global Static variable will be visible, certainly AutoIt itself will know (in all parts of the script) the same as the history of the ByRefAutoItAu3Check, but to add a control in Au3Check to help udf makers to be more save that their Global Static variable is not usedchangeedit outside the basic function of the udf

for the moment the only useful is that once created in UDF Global Static variable the user can not create another variable with that name, since Au3Check report it, and this helps a lot, but the user can changeedit it (in their functions ect ect) by mistake hmmmm, it would have been nice if the Au3Check try to check this too, I know that in the end everything will never be 100% save, but at least it would help a lot

Ciao.

Edited December 31, 2013 by DXRW4E

[Melba23]

DXRW4E,

I would say that it is up to the UDF author to create sufficiently individual names for the Global variables in the UDF so that they are extremely unlikely to be matched by anything created by the user - and also to limit the number of any Global variables to a minimum in the first place.

M23

P.S. Moved to Developer Chat.

[czardas]

I thought static variables were intended to be used as local within a function.

[guinness]

There isn't a difference between Global Static and Global. Is there?

[czardas]

Not one I'm aware of.

[DXRW4E]

Hi Melba23

I would say that it is up to the UDF author to create sufficiently individual names for the Global variables in the UDF so that they are extremely unlikely to be matched by anything created by the user

for the moment we all do so, is the only solution, but not its safe, for this asked to add in Au3Check (Optional) directive or something like that, to help more
 

and also to limit the number of any Global variables to a minimum in the first place.

is right, in all UDF, serve a maximum 1 or 2 Global Static variable
 

I thought static variables were intended to be used as local within a function.

no, also exists as a global
 

There isn't a difference between Global Static and Global. Is there?

for UDF yes

for the moment the only useful is that once created in UDF Global Static variable the user can not create another variable with that name, since Au3Check report it, and this helps a lot

Ciao.

Edited December 31, 2013 by DXRW4E

[DatMCEyeBall]

There isn't a difference between Global Static and Global. Is there?

Global $sGlobal = "Global text"
Global Static $sStatic = "Global Static text"
Global Const $sConst = "Global Const text"

$sGlobal = "new text" ; $sGlobal's value will be changed to "new text"
$sStatic = "new text" ; No change
$sConst = "new text" ; Au3Check reports changing a constant, AutoIT3 crashes with an error

[czardas]

Global $sGlobal = "Global text"
Global Static $sStatic = "Global Static text"
Global Const $sConst = "Global Const text"

$sGlobal = "new text" ; $sGlobal's value will be changed to "new text"
$sStatic = "new text" ; No change
$sConst = "new text" ; Au3Check reports changing a constant, AutoIT3 crashes with an error

 

Hmm, the static variable does change its value.

Edited December 31, 2013 by czardas

[guinness]

There is no file scope in AutoIt.

DatMCEyeBall,

Test again please.

Edited December 31, 2013 by guinness

[Melba23]

DatMCEyeBall,

Both the Global & Global Static variables change when I run that code:

Global $sGlobal = "Global text"
Global Static $sStatic = "Global Static text"

$sGlobal = "new text"
$sStatic = "new text"

ConsoleWrite($sGlobal & " - " & $sStatic & @CRLF)

which is exactly what I would expect.

M23

[DXRW4E]

Hmm, the static variable does change its value.

Global $sGlobal = "Global text"
Global Static $sStatic = "Global Static text"
Global Const $sConst = "Global Const text"

$sGlobal = "new text" ; $sGlobal's value will be changed to "new text"
$sStatic = "new text2" ;$sStatic's value will be changed to "new text2"
MsgBox(0,0,$sStatic)

yes they do, this is the point how to protect them in UDF, because in personal script does not need not have to do it does not make sense to do it

Edited December 31, 2013 by DXRW4E

[DatMCEyeBall]

Hmm, the static variable does change its value.

It does?

What version of AutoIT?

AFAIK Static variables should stay the same and only be declared once, after AutoIT passes the declaration again it ignores it.

Try this:

Global $sGlobal = "Global text"
Global Static $sStatic = "Global Static text"
Global Const $sConst = "Global Const text"

$sGlobal = "new text" ; $sGlobal's value will be changed to "new text"
Global Static $sStatic = "new text" ; No change
$sConst = "new text" ; Au3Check reports changing a constant, AutoIT3 crashes with an error'

Or

_CreateStatic() ; Outputs 1
_CreateStatic() ; Outputs 2

Func _CreateStatic()
    Local Static $i = 0
    $i += 1
    ConsoleWrite("$i = " & $i & @CRLF)
EndFunc

Edited December 31, 2013 by DatMCEyeBall

[guinness]

I am using v3.3.10.1 (need to upgrade today).

[czardas]

How to protect them - put them inside a function and declare them as local.

Edited December 31, 2013 by czardas

[DatMCEyeBall]

How to protect Globals - use constants

[guinness]

I still think Global and Global Static make no difference. Just use Global.

[DXRW4E]

I still think Global and Global Static make no difference. Just use Global.

yes is right, for the moment only this

the only useful is that once created in UDF Global Static variable the user can not create another variable with that name, since Au3Check report it, and this helps a lot

Global $sGlobal = "Global text"
Global Static $sStatic = "Global Static text"

Global $sGlobal = "new text" ; $sGlobal's value will be changed to "new text"
Global $sStatic = "new text2" ; No change
MsgBox(0,0,$sStatic)

;~ >Running:(3.3.10.2):C:\Program Files (x86)\AutoIt3\autoit3.exe "C:\Users\DXRW4E\Desktop\New AutoIt v3 Script (2).au3"    
;~ --> Press Ctrl+Alt+F5 to Restart or Ctrl+Break to Stop
;~ "C:\Users\DXRW4E\Desktop\New AutoIt v3 Script (2).au3" (5) : ==> Cannot make static variables into regular variables.:
;~ Global $sStatic = "new text2"
;~ Global ^ ERROR
;~ ->11:10:36 AutoIt3.exe ended.rc:1
;~ >Exit code: 1    Time: 0.423

but may do so, in order to work as they should, can not I speak with competence regarding C because I do not know much about C, but in C sees them Global Static seeuse only the files where they are being declared, in autoit this can be done with Au3Check and some (Optional) directive or something like that, where indicate the names of the functions that seeuseeditchange that variable

Ciao.

Edited December 31, 2013 by DXRW4E

[Melba23]

DatMCEyeBall,

Do you actually run these code snippets before posting them and confusing the hell out of everyone?

The first one you posted at #12 fails like this:

"M:\Program\Au3 Scripts\fred4.au3" (5) : ==> Cannot make existing variables static.:
Global Static $sStatic = "new text"
Global Static ^ ERROR

Which is again exactly what I would expect, having played around a lot with Static variables when they were first introduced.

 

AFAIK Static variables should stay the same and only be declared once, after AutoIT passes the declaration again it ignores it

Correct, as your second snippet shows. But that is of little relevance to the case in point.

M23

[czardas]

If you don't want the values to change then create Constants. Otherwise find another solution.

Global $sStatic = False

If $sStatic Then _StaticGlobal()

Func _StaticGlobal()
    Static $sGlobal = False
    $sStatic = $sGlobal
EndFunc

Code is intended as a kind of a joke.

Edited December 31, 2013 by czardas

[DXRW4E]

 

If you don't want the values to change then create Constants. Otherwise find another solution.

Global $sStatic = False

If $sStatic Then _StaticGlobal()

Func _StaticGlobal()
    Static $sGlobal = False
    $sStatic = $sGlobal
EndFunc

does not make sense (said this because it seems out of context), need first to understand the purpose of the Static  (for what is useful Static), and after the difference of the Local Static and Global Static

 

Ciao.

Edited December 31, 2013 by DXRW4E