<div><br></div><div><br><div class="gmail_quote"><div dir="ltr">On Wed, Feb 13, 2019 at 7:07 AM Ben Boeckel <<a href="mailto:ben.boeckel@kitware.com">ben.boeckel@kitware.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, Feb 12, 2019 at 14:01:34 -0800, JF Bastien wrote:<br>
> I'm confused as to why headers suddenly stop working.<br>
<br>
Because if, as a project, I port over to modules, I *still* have to<br>
maintain headers? I may as well not do modules at all at that point just<br>
due to maintenance costs.</blockquote><div dir="auto"><br></div><div dir="auto">Seems something a tool can do, if I understand what you have in mind. </div><div dir="auto"><br></div><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> > We need an intermediate representation that is *portable*.<br>
> >><br>
> ><br>
> We do?<br>
<br>
For projects which don't build zlib++ (as a strawman) as part of their<br>
build and instead assume that there is one provided by the system, yes.</blockquote><div dir="auto"><br></div><div dir="auto">I don’t think that’s true, based on what my platform offers. </div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
--Ben<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></div>