On Mon, 2007-05-21 at 17:09 -0700, John Meacham wrote: > On Tue, May 22, 2007 at 09:30:19AM +1000, skaller wrote: > > This is a VERY bad idea and breaks ISO rules. > > These symbols are reserved, and may not be defined by users. > > > > The correct way to handle this is to define your own > > symbols such as judy_int16_t etc. Otherwise you may conflict > > with a compiler upgrade or some other user that decided to > > break the rules. > > Please no, > > This is a huge pet peeve of mine, the correct thing to do is to use > the standard 'uint32_t' and whatnot internally everywhere, assuming an > ISO compliant compiler.
unit32_t etc is not required for an ISO compliant compiler ;( > For the non-iso ones an autoconf macro can fill in the needed typedefs. Absolutely not allowed. > I abhor interfaces that use GL_int, gints, judy_int32s or whatnot. I agree, but that is irrelevant. Just think about it. We cannot have two libraries both making these corrections in their own headers, because those libraries will then conflict. Therefore, if you're going to fix deficient headers you must fix them where all libraries can access a common fix. -- John Skaller <skaller at users dot sf dot net> Felix, successor to C++: http://felix.sf.net ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Judy-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/judy-devel
