i hate defines.txt!!

[Joel]

About the whole global/local thing: what I meant was that putting the actual text of your global defines at the beginning of all your logics instead of a #include directive would make it very hard to change the value of a global define. Recompiling all the logics would be fun by comparison.

[Chris Cromer]

I have no problems keeping track of variables and flags. What I do it when I use a flag or variable I write down which one I used in a txt file then before I assign a new flag or variable I check to see which flags and variables are used and make sure I don't use them.

[Nick Sonneveld]

I have no problems keeping track of variables and flags. What I do it when I use a flag or variable I write down which one I used in a txt file then before I assign a new flag or variable I check to see which flags and variables are used and make sure I don't use them.

Why don't you call this file defines.txt and include it with all your logic source

Seriously though.. I think the AGI Studio compiler needs some sort of way of automatically assigned variables/flags for your logics.  Maybe logics should get compiled to some sort of abstract object format and only get variables assigned when getting linked.

- Nick

[Chris Cromer]

The reason I don't use it as defines.txt is because I just write the flag or variable number. The only thing I ever change in defines.txt would be the about message and the version message.