On Tue, 19 Jul 2005 17:58:27 +0200 Tilman Sauerbeck <[EMAIL PROTECTED]> babbled:
> Sebastien HOUZE <[EMAIL PROTECTED]> [2005-07-19 15:02]: > > +#define MAXIMIZE 12 > > +#define MAXIMIZE_H 13 > > +#define MAXIMIZE_V 14 > > That's pretty ugly, magic values suck. Where do these come from? What > about putting them in an enumeration? etc ;) I think i have to accept some blame - a lot of e17 has these #defined enums. basically because i WANT to 1. hard-lock define the data type for saving/loading to an int or char etc. and 2. want constant values so they do not vary between compilations (eg ipc or config stuff) so SOME things are done in this style others done with enums where it isnt an issue. :) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] 裸好多 [EMAIL PROTECTED] Tokyo, Japan (東京 日本) ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
