Quote:
Originally Posted by The1Speck
So like GET and SET functions? Only way to accomplish what you're asking if I'm understanding correctly.
|
Yes that's what I was talking about. I see I'll have to write a few more natives to do exactly that.
Quote:
Originally Posted by Powerlord
When you have an #include line, it is replaced with the contents of the file during one of the preprocessor passes.
So... its OK to have an enum or constant in an include file as their values never change. On the flip side, putting a variable there ends up with each plugin having their own independent copy of the variable.
|
Own independent copy of the variable... do not want.
I suppose I'll just write a bunch of additional natives that get/set values on variables in the other plugin (like TheSpeck was mentioning). Keeping multiple copies sounds like a lot of unwanted bookkeeping work (especially if handles are involved, which it is in my case).
Thanks for the responses! I'll give it an attempt tonight/tomorrow and see if it works out well.