On Tue, Mar 26, 2013 at 1:42 PM, Alexis Menard <ale...@webkit.org> wrote:
> On Tue, Mar 26, 2013 at 5:40 PM, Dirk Pranke <dpra...@chromium.org> wrote: > > On Tue, Mar 26, 2013 at 1:29 PM, Benjamin Poulain <benja...@webkit.org> > > wrote: > >> > >> On Tue, Mar 26, 2013 at 1:20 PM, Dirk Pranke <dpra...@chromium.org> > wrote > >>> > >>> If we have consensus that we should just switch to paths relative to > >>> Source (or maybe a couple different options), that would be (IMO) a > big win. > >>> It sounds like Daniel & co. have already done the big bang conversion. > >> > >> > >> I think using full path would be a serious hit regarding hackability. > >> > >> I would rather spend some time tweaking my compiler to cache each > >> directory content than waste time finding where is every single header I > >> need to include. > >> > > > > Interesting. I have the exact opposite experience, having to paw around > to > > figure out where "Font.h" actually lives rather than just seeing > > "WebCore/platform/graphics/Font.h". > > But a modern IDE can easily solve that for you. You just click on the > header and it opens it for you. Xcode, QtCreator handles it very well. > > That said if you don't use an IDE then I understand your point :). > > I think to me the fact that the paths are spelled out is both one less action I have to do to get my question answered (I don't have to click), and a helpful reminder of the general layout of the code (and which directories I might need to care about in relation to a particular file). -- Dirk
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev