Printable View
See topic.
That is VERY annoying.
For the non-programmer types, globals have a TON of advantages over locals. Locals have a small advantage if you want to reuse the name, or a big advantage if you want to have, say, one defined variable track multiple health bars or such. In all other circumstances, globals are more efficient. Some people cry foul that it makes your code "sloppy" or "unreadable", but that's stupid.
ZScript actually does allow global variables and arrays. std.zh just doesn't define any since there is a limit of 256 currently. Also const int is basically the script version of a c #define in case anyone was wondering; can't recall if they obey normal scope rules though.
IIRC, it was when I tried to set one to a value that I encountered the problem, and it said something about defining non-constant globals.Quote:
Originally Posted by Gleeok
Is it an int or float?
As far as I know, only those work.
TBH, I don't remember at this point. I just remember it was a restriction that I didn't have to deal with in C#.
Here's the deal though a bunch of the types have a scope to one screen. So making a global pointer would cause it to return god only knows what when you change screens. It could be valid or not valid. There's no telling because ZASM is awful. Correct me if I'm wrong here @Gleeok .
I would of prefered globals of all types, actually. Error prone? Maybe. Smaller scripts and less typing? Sure.
Exactly, besides which programming involves a LOT of trial and Error, and a LOT of bug aversions in the first place. I understand some gamers need their hands held, but by the time you're at the level of an actual programmer, it's just annoying.Quote:
Originally Posted by Gleeok
Me too Omae, me too. I would make backbeard if i could have global npcs.
Backbeard eh? Is that a pirate with a really hairy back?Quote:
Originally Posted by Tamamo