<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Mar 26, 2013, at 1:40 PM, Dirk Pranke <<a href="mailto:dpranke@chromium.org">dpranke@chromium.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;"><div dir="ltr">On Tue, Mar 26, 2013 at 1:29 PM, Benjamin Poulain<span class="Apple-converted-space"> </span><span dir="ltr"><<a href="mailto:benjamin@webkit.org" target="_blank">benjamin@webkit.org</a>></span><span class="Apple-converted-space"> </span>wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div class="gmail_quote">On Tue, Mar 26, 2013 at 1:20 PM, Dirk Pranke<span class="Apple-converted-space"> </span><span dir="ltr"><<a href="mailto:dpranke@chromium.org" target="_blank">dpranke@chromium.org</a>></span><span class="Apple-converted-space"> </span>wrote<div class="im"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">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.</div></div></div></blockquote><div><br></div></div><div>I think using full path would be a serious hit regarding hackability.</div><div><br></div><div>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.</div><span class=""><font color="#888888"><br></font></span></div></blockquote><div><br></div><div>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".</div><div><br></div><div>At any rate, to be clear, I would be in favor of that change but I'm not expecting it to happen :).</div></div></div></div></div></blockquote><div><br></div><div>I'm with Dirk on this. Full path would help hackability for me.</div><div><br></div><div>I don't use an IDE, so I'll be typing more. But I spend more time reading code than typing code.</div><div><br></div><div>Also we have a lot of stupid in header file naming right now. For example the DFG calls the JSC::DFG::Node header "DFGNode.h", and puts it in JavaScriptCore/dfg/DFGNode.h. So we duplicate the namespacing of JSC::DFG::Node in both the filename and the directory name. Ridiculous! If we had a discipline to always include using paths relative to Source, then we could just rename it to JavaScriptCore/dfg/Node.h. That would make me happy.</div><div><br></div><div>-F</div><div><br></div><div><br></div><br><blockquote type="cite"><div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>-- Dirk </div></div></div></div>_______________________________________________<br>webkit-dev mailing list<br><a href="mailto:webkit-dev@lists.webkit.org">webkit-dev@lists.webkit.org</a><br><a href="https://lists.webkit.org/mailman/listinfo/webkit-dev">https://lists.webkit.org/mailman/listinfo/webkit-dev</a></div></blockquote></div><br></body></html>