<div dir="ltr">I mean, that's fair. :) We're certainly aiming to get to a world where that secondary build graph layer is machine-managed and generated from source. </div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Feb 1, 2019 at 9:24 AM Bjarne Stroustrup <<a href="mailto:bjarne@stroustrup.com">bjarne@stroustrup.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
On 2/1/2019 9:20 AM, Boris Kolpackov wrote:<br>
> Titus Winters <<a href="mailto:titus@google.com" target="_blank">titus@google.com</a>> writes:<br>
><br>
>> We've been doing explicit statements of the dependency chain for our<br>
>> codebase for almost 20 years, and I've literally never heard a new hire (or<br>
>> anyone else) say it is a "huge" burden.<br>
> The question is to what degree. I am sure you don't require new<br>
> hires to manually specify for each translation unit dependencies<br>
> on headers it includes, transitively?<br>
><br>
> But that would sure make for a nice hazing ritual.<br>
<br>
:-)<br>
<br>
<br>
Seriously, having manual dependency specification is inherently <br>
error-prone (independent double specification always is), as well as <br>
extra work. The fact that it is manageable for someone somewhere doesn't <br>
change that. I suspect its a skills, productivity, and scaling issue.<br>
<br>
> _______________________________________________<br>
> Tooling mailing list<br>
> <a href="mailto:Tooling@isocpp.open-std.org" target="_blank">Tooling@isocpp.open-std.org</a><br>
> <a href="http://www.open-std.org/mailman/listinfo/tooling" rel="noreferrer" target="_blank">http://www.open-std.org/mailman/listinfo/tooling</a><br>
_______________________________________________<br>
Tooling mailing list<br>
<a href="mailto:Tooling@isocpp.open-std.org" target="_blank">Tooling@isocpp.open-std.org</a><br>
<a href="http://www.open-std.org/mailman/listinfo/tooling" rel="noreferrer" target="_blank">http://www.open-std.org/mailman/listinfo/tooling</a><br>
</blockquote></div>