On Friday 2014-11-28 10:12 +0900, Mike Hommey wrote: > The downside from doing so, though, is that non-unified build *will* > be broken, and code "purity" (right includes in the right sources, > mostly) won't be ensured. Do you think this is important enough to keep > non-unified builds around?
Another disadvantage here is that it will make adding or removing source files harder, because you'll have to clean up the accumulated "nonunified" bustage that shows up when files are shifted around between unified files. (This might be somewhat harder to fix a year or two later than it is when causing it.) -David -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla https://www.mozilla.org/ 𝄂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914)
signature.asc
Description: Digital signature
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
