Re: [webkit-dev] Code Search for webkit.org

I usually search the copy of WebKit that's in the Chromium sub-index of code search. It's at most one day behind ToT WebKit (plus Code Search crawl/indexing delays): http://www.google.com/codesearch#search/&exact_package=chromium&q=file%3A%5Esrc/third_party/WebKit Mihai Mihai On Fri, Sep 30, 20

Re: [webkit-dev] Features defines: Platform.h vs build system

Speaking of macros, I'd like to add a COMPILER_SUPPORTS macro, so we can use it for incrementally introducing C++11 features such as variadic templates and rvalue references… - Anders On Oct 3, 2011, at 9:53 AM, Darin Adler wrote: > On Oct 3, 2011, at 8:23 AM, Adam Roben wrote: > >> I think

Re: [webkit-dev] Features defines: Platform.h vs build system

On Oct 3, 2011, at 8:23 AM, Adam Roben wrote: > I think the plan is outlined here: > . That’s it! I really want to do it! I noticed that one thing the plan doesn’t state is where the includes of the PortXXX.h files go. -- Darin ___

Re: [webkit-dev] Features defines: Platform.h vs build system

On Oct 3, 2011, at 10:51 AM, Darin Adler wrote: > But a while back, Maciej outlined a concept for where to put these platform > base include files; I don’t remember when that was or what the details were. I think the plan is outlined here: .

Re: [webkit-dev] Features defines: Platform.h vs build system

On Oct 3, 2011, at 6:35 AM, Balazs Kelemen wrote: > I think we lack a consistent way for setting up the set of feature defines. > Some of them are handled via Platform.h and some of them via the build > systems. Don't you think all should be handled the same way? This has came up > in my mind i

[webkit-dev] Features defines: Platform.h vs build system

Hi all! I think we lack a consistent way for setting up the set of feature defines. Some of them are handled via Platform.h and some of them via the build systems. Don't you think all should be handled the same way? This has came up in my mind in connection with the newly introduced CSS_F