Weird Compiler Behavior in PmoveSingle

[razorace]

Why does PmoveSingle treat char and int statments like 4 letter words? I can't get any of those type of statments to work there while it works fine in PM_weapon?

 

There's a workaround by doing all the int/char work inside a user made function, but it's still a pain in the butt.

[Wudan]

I thought PMoveSingle worked as the master Move function, calling functions as conditions met require.

 

Describe the odd behavior, because your problem sounds like my problem - but I haven't been messing with PMoveSingle all that much, but it seems like we might have the same problem.

[razorace]

Ok, it seems like it will allow new if and function statements but not ANY char or int stuff. It treats they like syntax errors.

 

I have no clue how/why the compiler is that picky, and it's very frustrating.

[Jaii der Herr]

all new variables must be at the top of an block.

 

for example at the begin of a function or at the begin of any "{"

But don't declare var's inside a loop

[razorace]

Already tried that. Maybe it's a compiler bug. I've already encountered a similar compiler bug while messing with the g_damage....