[JASS] Global decleration problem

[Cheezeman]

Can anyone give me a valid reason why these lines would give me a syntax error?

scope CHANGENAME initializer Initialize
//...
    globals
        private group targets
        private boolexpr allowed
        private integer Owner_Id
        private timer Timer
    endglobals
//...
endscope

Line 268: Syntax Error: group CHANGENAME__targets
Line 269: Syntax Error: boolexpr CHANGENAME__allowed
Line 270: Syntax Error: integer CHANGENAME__Owner_Id
Line 271: Syntax Error: timer CHANGENAME__Timer


Worked earlier today perfectly
Yes, I'm serious. Here's a picture:

(Just realized that pictures won't prove it since I can still highlight anything in the syntax checker. All I can give you is my word)

 

[Ciebron]

Don't think Syntax Checker work with vJass

 

[Cheezeman]

Don't think Syntax Checker work with vJass

If you check my error codes you will see that I am using JNPG for this map.
(I added a "scope" segment in the post now to make it more understandable)

 

[Viikuna]

TESH syntax checker is kinda useless, since it does not regonize any of this vJass stuff.

Just save your map to see if there is any errors. JassHelper will report them in that case.

 

[Cheezeman]

TESH syntax checker is kinda useless, since it does not regonize any of this vJass stuff.

Just save your map to see if there is any errors. JassHelper will report them in that case.

I said JNPG, not TESH

 

[Eleandor]

TESH is part of JNGP.

 

[Viikuna]

Oh, sorry. Should have checked that screenshot.


You sure that dont have disable vJass syntax checked?

 

[Cheezeman]

TESH is part of JNGP.

Yes I know, but I don't use their syntax checker

Oh, sorry. Should have checked that screenshot.


You sure that dont have disable vJass syntax checked?

Well, it does convert the private globals into ScopeName+__+VariableName, right?
So... I guess not

Damnit I think I gotta re-install JNPG and try again.
Anyway this is a really wierd bug

 

[Eleandor]

Yes I know, but I don't use their syntax checker

Sorry.

Could you post the stuff below the syntax errors? I've had bugs where the line of the error is not related to the error...

 

[Cheezeman]

Sorry.

Could you post the stuff below the syntax errors? I've had bugs where the line of the error is not related to the error...

Yes I can

        constant real CHANGENAME___INCREASE_PER_INTERVAL = 10.
        constant real CHANGENAME___DECREASE_PER_INTERVAL = 10.
        constant real CHANGENAME___INTERVAL              = .20
        constant real CHANGENAME___MAX_AREA              = 1000.
        constant real CHANGENAME___MIN_AREA              = 300.
        constant real CHANGENAME___INITIAL_AREA          = 500.
        constant effect CHANGENAME___EXPLOSION           = 
        group CHANGENAME__targets
        boolexpr CHANGENAME__allowed
        integer CHANGENAME__Owner_Id
        timer CHANGENAME__Timer
// processed:         unit array CHANGENAME__User[7]
// processed:         real array CHANGENAME__SpellX[7]
// processed:         real array CHANGENAME__SpellY[7]
// processed:         real array CHANGENAME__Area[7]
// processed:         boolean array CHANGENAME__HasReachedMaxCap[7]

trigger l__library_init

//JASSHelper struct globals:
integer array s__TimerUtils__data
integer array s__2TimerUtils__data
integer array s__3TimerUtils__data
integer array s__4TimerUtils__data
integer array s__5TimerUtils__data
integer array s__6TimerUtils__data
integer array s__7TimerUtils__data
//etc...

 

[Viikuna]

Could it be?:

        constant effect CHANGENAME___EXPLOSION           =

It is = ( nothing here )

 

[Eleandor]

Yeah, that's got to be it.

 

[Cokemonkey11]

if you want it to be nothing remove the =, I believe that will fix it.

 

[LeP]

if you want it to be nothing remove the =, I believe that will fix it.

No.
Constant variables have to be initialized.
But a constant effect is kinda useless, imo.

 

[Cheezeman]

Could it be?:

        constant effect CHANGENAME___EXPLOSION           =

It is = ( nothing here )

Yup, that's it. Epic mistake
+Rep to you and Eleandor.

if you want it to be nothing remove the =, I believe that will fix it.

No, that will just cause another syntax error, constants have to be initialized.

But a constant effect is kinda useless, imo.

Constant variables are faster than regular variables and will never change, and since mine doesn't ever change in the map I decided to make it constant (to make it faster and avoid stupid bugs which changes it)
If you'd like one single global variable like "Temp_Effect" you're absolutely right, they shouldn't be constant. But in mattes like this - when they don't change ever - always use constants.

 

[LeP]

Well, i never used any constant effect so i wrote imo (in my opinion).
I never use something like that because for effects on units i can use sphere and for effect that are shown the whole i time i use doodads or units.

 

[Deaod]

constant handles ARE useless. And cause bugs when optimizing.

 

[Cheezeman]

constant handles ARE useless. And cause bugs when optimizing.

ok?
not that I use them that much, but why?

btw I did change that effect to a string, it was a mis-match with types