Comment #8 on issue 448 by mike.emmel: X11 defines True and False http://code.google.com/p/v8/issues/detail?id=448
I don't know what to say then. To be honest I never expected you to fix stomping system headers given your willing to clash with windows.h not much I can say. Look I can't fix this except by fully wrapping your api and never exposing your types. Anyone that tries to use your library is going to have fun playing ifdef games. In chrome I just posted and example where even the nsapi wrapper header that hides your types is blown. If you want to stomp all over the namespaces of code based that have been around for thirty years or more and are the core parts of many operating systems then enjoy. Fix chrome so they don't have to munge the nsapi.h header because of your namespace pollution and post it on the bug. And yes these code bases window X11 etc have problems but the fact they define common names is a big reason why C++ has namespaces in the first place. I found a nice book online that it looks like you guys need to read. http://books.google.com/books?id=4Kb_1sKprCMC&pg=PA36&lpg=PA36&dq=namespace+pollution+programming&source=bl&ots=v7iEL1xZGW&sig=nJXx5A6FciYPTaW9TArVtnWRagY&hl=en&ei=Pm28Sv6fJsnflAe95piZBA&sa=X&oi=book_result&ct=result&resnum=4#v=onepage&q=namespace%20pollution%20programming&f=false -- 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 -~----------~----~----~----~------~----~------~--~---
