When did JassHelper get this messed up?

[Jesus4Lyf]

library MyDog initializer OnInit
    globals
        private integer 5=2
    endglobals
    private function OnInit takes nothing returns nothing
        call BJDebugMsg(I2S(5)) // prints 2
        set 5=7
        call BJDebugMsg(I2S(5)) // prints 7
    endfunction
endlibrary

Mmm... defines! <_<

... Err... Could we always do that?
And I wonder when he'll fix that.

 

[Azlier]

I don't expect it to work with scopeless globals, however. I think the only reason that works is because it compiles into MyDog__5.

 

[Jesus4Lyf]

Of course. Imagine the unreadable code factor, though...

Edit:

library MyDog initializer OnInit
    globals
        private constant string 5="5"
    endglobals
    private function OnInit takes nothing returns nothing
        call BJDebugMsg(5)
    endfunction
endlibrary

 

[Azlier]

That works? Madness.

 

[Anachron]

It's not a bug. It's most likely what Azlier already said. Its because scopes / librarys will overwrite the variable name, so making it valid.

"It's not a bug, it's a feature!"

 

[Jesus4Lyf]

It's not a bug. It's most likely what Azlier already said. Its because scopes / librarys will overwrite the variable name, so making it valid.

"It's not a bug, it's a feature!"

Did you just tell me that

library MyDog initializer OnInit
    function interface 4 takes integer 6 returns nothing
    function interface 7 takes nothing returns nothing
    globals
        private 4 8
        private 7 3=9
        private string 2
    endglobals
    function kk takes integer I returns nothing
        set 2=I2S(I)
    endfunction
    private function OnInit takes nothing returns nothing
        set 8=kk
        call 8.evaluate(3)
        call BJDebugMsg(2)
    endfunction
endlibrary

is working as intended? Even Blizzard doesn't do that.

 

[Anachron]

MyDog__4 is a valid name for a variable.

It's ugly to use, but there could be situations in which this is useful.

 

[Jesus4Lyf]

Lol dude...

library MyDog
    private keyword 3
    struct four
        four 3=2
        private static method onInit takes nothing returns nothing
            local integer this=1
            call thistype.create()
            call BJDebugMsg("For three to be "+I2S(3)+", just follow my clue...")
        endmethod
    endstruct
endlibrary

:nuts:

library MyDog initializer OnInit
    private keyword 4
    private function 4 takes nothing returns integer
        return 4+4
    endfunction
    private function OnInit takes nothing returns nothing
        call BJDebugMsg(I2S(4()))
    endfunction
endlibrary

In case you didn't realise 4+4=2, or some other value depending on how much vJass you use...

 

[Anachron]

Why would you name a variable like a number? It's stupid.

 

[Jesus4Lyf]

Why would you name a variable like a number? It's stupid.

Because I like to hard code the number of players in my map like a magic number, and then change it later without changing my code?

library MyDog initializer OnInit
    globals
        private integer 8=12
    endglobals
    private function OnInit takes nothing returns nothing
        local integer i=8
        loop
            set i=i-1
            call BJDebugMsg(GetPlayerName(Player(i)))
            exitwhen i==0
        endloop
    endfunction
endlibrary

That's the kind of reason it's a bug.

Edit:
Or maybe we like to divide by 0, but decide that maybe that's not so bright after all...

library MyDog initializer OnInit
    globals
        private integer 0=1
    endglobals
    private function OnInit takes nothing returns nothing
        call BJDebugMsg(I2S(3/0))
    endfunction
endlibrary

 

[Anachron]

Lol! Hardcode the number to be magic? There is no, really no advantage of this.

 

[Prometheus]

private constant integer 12 = 12 // Number of players in the map.

Win

 

[Jesus4Lyf]

Moar syntax!

library NoMoreVariableNames
    private keyword 1=7
    private keyword 2=5
    private keyword 3=2
    private keyword 4=3
    private keyword 5=4
    private keyword 6=1
    private keyword 7=5
    private keyword 8=7
    private keyword 9=2
    private keyword 0=50
    
    struct NoMoreVarNames
        integer 2=97
        string 9="king"
        string 6=9
        integer 0=2
        method operator 7 takes nothing returns string
            call this.destroy() // lol??
            return R2S(SquareRoot(this))
        endmethod
        private static method onInit takes nothing returns nothing
            local thistype this=thistype.create()
            call BJDebugMsg(I2S(0))
            call BJDebugMsg(6)
            call BJDebugMsg(7)
            set this=thistype.create()
            set this=thistype.create()
            call BJDebugMsg(7) // 7 is changin..
            set this=thistype.create()
            set this=thistype.create()
            set this=thistype.create()
            call BJDebugMsg(7)
        endmethod
    endstruct
endlibrary

 

[Prometheus]

Screenie of output?

 

[Jesus4Lyf]

Just run it... lol

the =x after keyword does nothing, just confuses.
"call BJDebugMsg(7)" displays the square root of the current struct (after destroying it).
That's about all of interest.

 

[chobibo]

Anyone tried reporting the bug? I think it's minor since it's unconventional to use numbers as variable names, I know I won't.

 

[codemonkey]

globals
    string 42 = "The meaning of life"
endglobals

I recommend applying this patch to all of your maps.

 

[Sickle]

That does not compile, codemonkey. A variable name cannot be an integer. The reason it works with private variables is because they are named ScopeName__Variable within the map script.

 

[Narks]

I guess your library can't share the secret of life then.

 

[Jesus4Lyf]

This has been fixed.