Comment #2 on issue 448 by mike.emmel: X11 defines True and False http://code.google.com/p/v8/issues/detail?id=448
In practice its not all that easy esp with library headers. Technically its a xlib issue they should have don XTrue or XFalse. But to late to change them. But thats why defining variants of true and false in a library is a really bad idea. I disagree it poor programming practice and its a mistake in XLib and a mistake in V8. Equating true and false issues for library headers to limiting yourself is ridiculous hyperbole. Your just ignoring a bad design decision for a library header. If you google you will find that libraries that define variants of true and false are always problematic to deal with. For that matter the new -> New trick is just as bad. If you really want to do this then the puplic header should have V8_ and use a helper header to ifdef the easy to type names. Or you can ifdef potential clashes from short common words in one header. Name clashes and the resulting use of prefixes in library headers is a serious issue not one that should be blithley ignored with comments about limiting yourself. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev -~----------~----~----~----~------~----~------~--~---
