Hi David, Okay, will do! Thanks, and sorry for the spam. I didn't see the message in my own list archives, which is why I thought it never made it. Now I just have to figure out what happened on my end. ;-)
Kevin On Sep 23, 2008, at 9:32 AM, David Kilzer wrote: > Hi Kevin, > > The original message did make it to the list, but no one replied. > > I think the best approach is to simply create a bug on > bugs.webkit.org and attach a patch for review (since the wx port is > apparently the only one "feeling the pain" right now :). > > Dave > > > On Tue, 9/23/08, Kevin Ollivier <[EMAIL PROTECTED]> wrote: > >> Hi all, >> >> I sent this message to the mailing list yesterday, but it >> seems it >> never made it, so I'm resending. >> >> Kevin >> >> Begin forwarded message: >> >>> From: Kevin Ollivier <[EMAIL PROTECTED]> >>> Date: September 22, 2008 12:13:24 PM PDT >>> To: [email protected] >>> Subject: Rename TypeInfo -> JSTypeInfo? >>> >>> Hi all, >>> >>> We're having a problem on the Windows version of >> wxWebKit where >>> #include <typeinfo> is actually now including >> JavaScriptCore/kjs/ >>> TypeInfo.h, which needless to say is not a good thing. >> ;-) I think >>> this problem stems from the fact that we (the wx port, >> that is) >>> don't use the 'framework' approach for JSC >> headers yet (and thus >>> need JavaScriptCore/kjs on our include path), but I >> think in general >>> it's good practice to avoid using system header >> names just for >>> readability purposes. Does anyone see a problem with >> renaming >>> TypeInfo to JS(C)TypeInfo, both header name and class? >>> >>> Thanks, >>> >>> Kevin >> >> _______________________________________________ >> webkit-dev mailing list >> [email protected] >> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
