About VERGE


 
#define 2-pass?
Displaying 1-4 of 4 total.
1
Please enter a numerical value for the importance of this sticky.
Enter 0 to unsticky.
mcgrue
No need to do this this build, but what does everyone think about having the compile do a sweep for all #defines before replacing them, thereby letting a library that defines something be included after a related library using something in the first library's domain.

Not c-like, but vec mentioned it as a possibility before and I'm finding it'd be a small boon tonight.

I can go either way, really, as it's not too terrible an inconvenience, but I thought I'd write it down as it came to mind.

Posted on 2005-07-03 00:35:21

janus
This may actually reduce the utility of #defines. Just FYI.

Posted on 2005-07-03 06:16:25

mcgrue
Howso?

Posted on 2005-07-03 06:35:14

gannon

 
#define errorcode log



errorcode('my error');



#define log messagebox



errorcode('my second error');


remember changes that will effect existing code must be made with caution
(sorry for posting here)

Posted on 2005-07-03 07:38:15


Displaying 1-4 of 4 total.
1
 
Newest messages
I Like Ham.
in Castle Heck
(by ThinIce on 2018-08-17)
Steamworks Integration
in VERGE Developers Forum
(by Eldritch05 on 2018-08-16)
Entity Issues
in VERGE Help
(by Rysen on 2018-06-05)
Epic of Serinor: Dawnshadow
in General Discussion
(by Rysen on 2018-05-13)

Ben McGraw's lovingly crafted this website from scratch for years.
It's a lot prettier this go around because of Jon Wofford.
Verge-rpg.com is a member of the lunarnet irc network, and would like to take this opportunity to remind you that regardless how babies taste, it is wrong to eat them.