[vJASS] Private isn't working as it should

[Starquizer]

While I was learning some vJASS, I stumbled upon this strange thing:

this is what I typed in the trigger:

scope human
private function f takes nothing returns nothing
endfunction
endscope

scope nightelf
private function f takes nothing returns nothing
endfunction
endscope

scope orcs
private function f takes nothing returns nothing
endfunction
endscope

scope undead
private function f takes nothing returns nothing
endfunction
endscope

and the generated script is:

// scope human begins
function human___f takes nothing returns nothing
endfunction
// scope human ends

// scope nightelf begins
function nightelf___f takes nothing returns nothing
endfunction
// scope nightelf ends

// scope orcs begins
function orcs___f takes nothing returns nothing
endfunction
// scope orcs ends

// scope undead begins
function undead___f takes nothing returns nothing
endfunction
// scope undead endss

from what I understand private works by adding scopename(random digit)__ , now all I see is the scopename___ (3 underscores) why is that ?

 

[Crazed_seal2]

Its possibly just how its generated. No big deal.

 

[mckill2009]

the purpose of scopes and libraries mainly for encapsualtion/order of code's placement
and you can declare functions with the same name without colliding each other, as for
your question why there are underscores(2 or 3), well the Jasshelper answers it...

A double _ is used because we decided that it is the way to recognize preprocessor-generated variables/functions, so you should avoid to use double __ in your human-declarated identifier names. Being able to recognize preprocessor-generated identifiers is useful when reading the output file (for example when PJass returns syntax errors).

 

[Starquizer]

The problem with (3underscores) is that I was able to call a private function outside the library, which opposes the function of "private" keyword

 

[overcold_ice]

you're wrong . . .

for library/scopes:
- they are capsules to place your codes
- private things inside it will have its name become LIBRARY_Name + SCOPE_PRIVATE + THING_Name
- public things inside it will have its name become LIBRARY_Name + "_" + THING_Name
- things with no private/public prefix will be counted as a public one, but here's the difference:

library X
    public function Y takes nothing returns nothing
    endfunction
    
    function Z takes nothing returns nothing
    endfunction
endlibrary

library A requires X
    function XYZ takes nothing returns nothing
        // do nothing, but shows how those encapsulation works
        call X_Y() // public
        call Z() // non-public, and not private too
    endfunction
endlibrary

and it's not always "___" (3 underscores), but it can be 2 (if i heard it right)
to detect it, use SCOPE_PRIVATE
and logically, because it's a SCOPE_PRIVATE variable that's located on each encapsulations, the number of underscores for a library/scope is always the same, but can be different with other libraries/scopes

 

[Luorax]

By reading the JASSHelper manual you could have easily avoided opening another useless thread. http://www.wc3c.net/vexorian/jasshelpermanual.html#lib

The way private work is actually by automatically prefixing scopename(random digit)__ to the identifier names of the private members. The random digit is a way to let it be truly private so people can not even use them by adding the preffix themselves. A double _ is used because we decided that it is the way to recognize preprocessor-generated variables/functions, so you should avoid to use double __ in your human-declarated identifier names. Being able to recognize preprocessor-generated identifiers is useful when reading the output file (for example when PJass returns syntax errors).

Tis language was made for a game; it's evolved a lot already and it's way better than it used to be. It's not the compiler's task to protect the coder from himself.

 

[Starquizer]

you're wrong . . .

I am sure of this, yesterday I ran lots of tests on the output script in the JNGP and I am sure that I was able to call the private function with (3) ___ outside the library. What I am posting is exactly what I typed in the trigger and what was in map.j

 

[Troll-Brain]

The thing is that you're not supposed to call the "jassified" code of vJass, just the vJass code.
This way it's private.
I don't see why you would directly use the jasssified code, that's senseless ...

 

[Starquizer]

The thing is that you're not supposed to call the "jassified" code of vJass, just the vJass code.
This way it's private.
I don't see why you would directly use the jasssified code, that's senseless ...

I understand what you mean but I am just trying to learn vJASS so I stumbled upon this issue.

 

[Troll-Brain]

That is not an issue, since i hardly see why you would use the "jassified" code instead of the vJass one.
Get the fact that vJass is full of "hacks", while it's good to see how the jass code is generated behind the scene, you must not directly use this "hidden" jass code.

After all, vJass is "just" a jass preprocessor.

 

[Berb]

There really isn't any such "thing" as private. Once code is compiled it is just a memory location. This memory location can be referenced, like any other memory location.

 

[mckill2009]

its just an identifier anyway for the processor, for sure 95% of humans dont want to name their function like this...
function blah___hh takes...

 

[overcold_ice]

its just an identifier anyway for the processor, for sure 95% of humans dont want to name their function like this...
function blah___hh takes...

worst thing:

library ONE
    private scope TWO
        private function THREE takes nothing returns nothing
        endfunction
    endscope
endlibrary

// manual naming
function ONE___TWO___THREE takes nothing returns nothing
endfunction

 

[Bribe]

Because it's either 2 or 3 underscores, half the time it will compile if you write out LibraryName__FunctionName, the other half it won't.