Class and local variable of same name

[icuurd12b42]

I just spent 4 hours chasing after a ahk Bug because I used a local variable the same name as a Class, in 2 different scripts that call each other, which had the side effect of turning them 2 local variables into a global... and nuking the class

Simplified here is a short example

Code: Select all

Class Something
{
    SomeFunc()
    {
        MsgBox, Something
    }
}
Func1()
{
    something := 10
}
Func2()
{
    something :=1
    Func1()
    Something.SomeFunc() ;gone
    return something
}
F1::
t := Func2() ; will return 10 instead of 1
msgbox,%t%
return

[nnnik]

That's why you should give your classes meaningful names

[icuurd12b42]

I'll be more careful and go Old school with the c prefix : CMyClass

[Helgef]

That is why you should declare variables as local . Although, about 100 % of the shared around here code doesn't, issues seems to be mostly limited to people missing this in the docs,

When the script is loaded, this constructs an object and stores it in the global (or in v1.1.05+, super-global) variable ClassName.

source

Also, if you use v2. you will get an error when you try to use the class after you have overwritten the reference in the variable className. Eg,

Code: Select all

test:=""
test.f() ; Error on v2, v1 is silent
class test{
	f(){
	}
}

This is of course very convenient and you will save about 4 hours of scratching your head

Cheers.

[icuurd12b42]

indeed
when is v2 coming out and will there me a v1 -> exporter? I'm a little worried doing the stuff I'm doing in v1