structs question

[WereElf]

If I do this:

struct a
    integer i = 0
endstruct

would it be the same as this:

struct a
    integer i

    static method create takes nothing returns thistype
        local thistype this = thistype.allocate()
        set this.i = 0
        return this
    endmethod
endstruct

Or would the 1-st way not always have i set to 0 upon creation? xP

 

[LeP]

You could always just look at the generated code. It's in jngp/logs/output{,_}war3map.j

struct foo
    integer x = 7
endstruct

becomes

//Generated allocator of foo
function s__foo__allocate takes nothing returns integer
 local integer this=si__foo_F
    if (this!=0) then
        set si__foo_F=si__foo_V[this]
    else
        set si__foo_I=si__foo_I+1
        set this=si__foo_I
    endif
    if (this>8190) then
        call DisplayTimedTextToPlayer(GetLocalPlayer(),0,0,1000.,"Unable to allocate id for an object of type: foo")
        return 0
    endif

   set s__foo_x[this]= 7
    set si__foo_V[this]=-1
 return this
endfunction

As you can see it actually set's the value in the allocator so this would work too:

struct foo
    integer x = 7
  
    static method create takes nothing returns thistype
        local thistype this = allocate()
        call BJDebugMsg(I2S(this.x)) // prints 7
        return this
    endmethod
endstruct

 

[IcemanBo]

As a rule of thumb the create function should handle initializations, for maintainability reasons, at least for bigger codes. Also, in case you switch to custom allocation, it would break it of course.
But yes, it works.

 

[WereElf]

Okay, thanks