Apparently, in at least C++, the evaluation order of static const members is undefined. Someone get me Bjarne Stroustrup's head, right now.
-
Oh... One common workaround is to create a struct used by a single global variable containing all the globals that need consistent initialization order (in Java parlance, a singleton), because normal class/struct members have defined order. struct { // stuff here } globals;
No-go on that one, my man. Due to various engine constraints which I can't/won't get into here, going that route would more or less double our UI system's static memory overhead.
Current plan is to just bite the bullet and change all the static consts to #define-s.
-
-
Ah if they really are all consts, and simple values at that, yes you're better off letting the preprocessor do it. I'm sorry you had to find out the hard way.
-
Me too ;)
Keskustelun loppu
Uusi keskustelu -
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.