[Solved] Array Sizes

[Faith]

Hey guys, quick question. I've noticed people change the array size shown in the image below.

What I want to know is why bother changing it?
What does it do exactly?

I've used array variables many times before, and I've never once changed the value to anything other than 1.

What's up with that?

Any help provided is appreciated.

 

[deathismyfriend]

only change it for dialogs, timers. other than those leave it at 1. the reason for changing those is that they need to be initialized when the map starts. the higher the number the more that gets initialized.

 

[Faith]

Why does it only matter for those?

 

[deathismyfriend]

the reason for changing those is that they need to be initialized when the map starts. the higher the number the more that gets initialized. sry i edited the top post after u saw it

 

[Faith]

Alright, that makes sense I guess.. Haha. ^_^
I appreciate it. +rep

 

[deathismyfriend]

np and thx for the rep.

 

[Nestharus]

Huh? They don't need to be initialized...

Always keep it at 1, always

People who put it above 1 are noob, lol


Unless initialization in GUI creates timers/dialogs rather than nulls them? :|

If that's the case, lame, at which point I'd still say to always keep it at 1 and destroy the timer/whatever at 0.

 

[Faith]

Okay, thank you! ^_^

 

[deathismyfriend]

ya it creates them in GUI rather than nulls them. it is really stupid.

you have to set the arrays higher than 1 for these otherwise you cant use anything above one. so player number of triggering unit doesnt work. no more MPI for these unless initialized in variable editor

 

[Nestharus]

You just create them yourself when you need them... it's called instancing >.<

Or you initialize it yourself :\

It doing the initialization via creation is majorly messed up

edit
I hate GUI.. seriously, I want nothing to do with it ever. It's so awful... wow

function InitGlobals takes nothing returns nothing
    local integer i= 0
    set i=0
    loop
        exitwhen ( i > 10 )
        set udg_test[i]=CreateTimer()
        set i=i + 1
    endloop

endfunction

 

[deathismyfriend]

lol ik what u mean there i cant stand gui anymore lol but ill still help someone when they need it.

 

[Dr Super Good]

The size field guarantees that size indices will be initialized. Reading from an uninitialized index causes a thread crash. Where this is useful is if you only ever need code that first reads the value and then writes something back (such as incrementing an integer). The size field saves you having to initialize it manually at some other time.

It is very bad for tasks where you write first and read back later. Examples are dynamic storage system (starts empty, you add data to it) or complex structures that you do not want to exist before they are required (you create a group on demand, not when the game starts).

Using a size of 16 is perfectly fine for an integer array counting player kills (you want it to start at 0 anyway).
Using a size of 1 is perfectly fine for an integer array that counts the cycles a custom ability will use that dynamically creates instances (you initialize the index to some number when the index is required for use).

 

[Nestharus]

Reading from an uninitialized index causes a thread crash.

False

 

[Dr Super Good]

False

You have any evidence at all to back that up? I have seen dozens of problems related to uninitialized variables causing a thread crash. Maybe it is uninitialized local variables but it seems strange that it should only be the one type and not the other.

Test function.

globals
    integer test
endglobals

function Trig_Untitled_Trigger_001_Actions takes nothing returns nothing
    local integer test2
    call BJDebugMsg("local variable test")
    call BJDebugMsg(I2S(test2))
    call BJDebugMsg("global variable test")
    call BJDebugMsg(I2S(test))
    call BJDebugMsg("global to local variable signment test")
    set test2 = test
    call BJDebugMsg(I2S(test2))
endfunction

Only "call BJDebugMsg("local variable test")" is executed. The line "call BJDebugMsg(I2S(test2))" is causing a thread crash.

Attempt with globals...

globals
    integer test
endglobals

function Trig_Untitled_Trigger_001_Actions takes nothing returns nothing
    local integer test2
    //call BJDebugMsg("local variable test")
    //call BJDebugMsg(I2S(test2))
    call BJDebugMsg("global variable test")
    call BJDebugMsg(I2S(test))
    call BJDebugMsg("global to local variable signment test")
    set test2 = test
    call BJDebugMsg(I2S(test2))
endfunction

Only "call BJDebugMsg("global variable test")" is executed. The line "call BJDebugMsg(I2S(test))" is causing a thread crash.

Now for arrays...

globals
    integer array test
endglobals

function Trig_Untitled_Trigger_001_Actions takes nothing returns nothing
    local integer array test2
    call BJDebugMsg("local variable test")
    call BJDebugMsg(I2S(test2[0]))
    call BJDebugMsg("global variable test")
    call BJDebugMsg(I2S(test[0]))
    call BJDebugMsg("global to local variable signment test")
    set test2[0] = test[0]
    call BJDebugMsg(I2S(test2[0]))
endfunction

All of it runs. What this proves is that JASS is the biggest piece of garbage one can ever use. While what I did say does apply to non arrays, JASS some how thinks arrays are different and operates completely differently on them. From this, we can assume that this is a bug with arrays (it is meant to crash the thread but instead is reading raw memory values) probably as a result of an optimization.

You should always initialize a variable before using it. In JAVA it is illegal to use an uninitialized variable. In C/C++ uninitialized variables might have any kind of memory garbage written to them and are a very common cause of errors and crashes.

 

[Nestharus]

Reading from an uninitialized index causes a thread crash

Your post said index, not scalar, thus your post was false, lol.

 

[Dr Super Good]

However there is no logical reason why reading from an uninitialized non-array will crash the thread yet reading from a non-initialized array does not.

 

[Nestharus]

However there is no logical reason why reading from an uninitialized non-array will crash the thread yet reading from a non-initialized array does not.

I said nothing about scalars, nor did you. Your original statement was on arrays crashing the thread when they weren't initialized, and I called you on your bs. Scalars had nothing to do with this =).

There is no way you can interpret setting an index as a scalar, lol.

 

[Orthane]

This went from helping someone into a pissing contest. I found the thread rather entertaining from start to finish. Also I do believe ArchAnge1 only works in GUI. So yeah.. Jass in this thread doesn't help the owner of the thread.

 

[deathismyfriend]

thread is solved anyways

 

[Orthane]

thread is solved anyways

Was solved 12 to 14 posts ago.

 

[deathismyfriend]

Was solved 12 to 14 posts ago.

ik lol