On 2012-02-28, at 17:11, Eric Seidel <[email protected]> wrote: > I'm fine with Source/wtf. Very easy to implement.
I think this has the potential to cause problems. It would lead to adding the Source directory to the header search path for some build systems, which would cause all sorts of weird #include styles to work even though we don't want to support them. I'd suggest sticking with Source/WTF and the code inside a wtf subdirectory, and we can consider further reorganisation down the line if necessary. - Mark > > On Tue, Feb 28, 2012 at 4:59 PM, Geoffrey Garen <[email protected]> wrote: >> My current plan is to have a WTF/wtf directory to avoid this exact issue. :) >> >> >> "WTF/wtf" makes the think, "WTF?" -- which is a fun mental onomatopoeia, but >> probably not a great design. >> >> Just plain "Source/wtf" looks better to me. >> >> And to avoid the annoyance of 131 files in the root WTF directory. >> >> >> I'd prefer to solve this problem -- if it is a problem -- orthogonally. >> >> Geoff _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
