<div dir="ltr"><br><div>We don't need it and a lot of us believe we need to not have it.</div><div>The price for this level of indirection, as you say is quite high on tooling. the benefits un-existant.</div><div><br></div><div>The evolution working group and the authors of the module proposal seem afraid to over specify - while SG-15 thinks<br></div><div>leaving things as they are will lead for decades of pain. At least, I certainly think so.</div><div><br></div><div>We have a lot of experience in other languages for deterministic and direct name -> file mapping, very little for having the module name solely in the source.</div><div><br></div><div><br></div><div>As for name collision... It's not a problem. It would even be a good thing to make sure not to have duplicated file names: </div><div>Module identifier needs to be unique in a program, so asking the same of files is reasonable.</div><div><br></div><div><br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 4 Feb 2019 at 02:20 Scott Wardle <<a href="mailto:swardle@gmail.com">swardle@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all, <br>
<br>
I have been looking for some information why do we need a level of indirection from module name to module interface file name. Why are modules names need a different system then header names. <br>
<br>
I have hear that Microsoft was having some problems with name collision. Is there more concrete information about the problem that Microsoft or other companies were having? <br>
<br>
If you have a name collision today with headers we would just make another library that wraps one of the two colliding headers. I name the public header of this new library something different and problem solved. <br>
<br>
So I don’t understand why are we paying for this level of indirection but I probably just don’t understand the problem. <br>
<br>
Scott <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>