<div dir="ltr"><div>Not really namespace related, but:</div><div>Most of the commercial/free/open source Delphi/FPC libraries are backward compatible to D7-D6 (including all Delphi-win32 versions)</div><div>That comes with a cost (a bless) of not using new language syntax (as much as possible).</div>
<div>And typically include a long-long ".inc" that instructs the compiler to be as much convservative as it can (fighting Delphi cross-version incompatibilities)</div><div> </div><div>So from language environment perspective, the hard usage of "namespaces" is most likely will be limited to a certain set of projects.</div>
<div> </div><div>thanks,</div><div>Dmitry</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Oct 25, 2013 at 10:18 PM, Fabrício Srdic <span dir="ltr"><<a href="mailto:fabricio.srdic@gmail.com" target="_blank">fabricio.srdic@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>I know I'm a newbie in fpc, but I don't see backward compatibility a reason enough to leave to implement some improvements, like organize the<br>
base units of the fpc into proper namespaces.<br>
<br></div>As Michael and Sven said, if Delphi itself is not fully compatible among versions, why should fpc be?<br><div><br>According to the on-line documentation, fpc has five units that are specific to the Unix context. So, why not keep them in a Unix specific namespace? If we have several elements that are platform-independent, why not keep them in a specific namespace, like e.g "System"?<br>
<br>As the number of units of the fpc increases, keeping related elements logically organized can even facilitate maintenance tasks.<br><br>To a novice like me, would be easier to locate and to identify what elements which are present in a e.g Windows.API.Messages or Windows.API.Mutex unit than in a huge Windows unit.<br>
</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">2013/10/25 Michael Van Canneyt <span dir="ltr"><<a href="mailto:michael@freepascal.org" target="_blank">michael@freepascal.org</a>></span><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
<div><br>
<br>
On Fri, 25 Oct 2013, Marco van de Voort wrote:<br>
<br>
</div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
No one forces anything. You can perfectly set the default namespace to<br>
'fpc' (or whatever) in the default config file, and all should compile as it was.<br>
</blockquote>
<br>
Yes. One can live with the XE2+ renaming at the cost of renaming units,<br>
potentially fixing breakage later, and a lot of adaptation of existing<br>
configuration, scripts etc.<br>
<br>
But I repeat: what is the hurry?<br>
</blockquote>
<br></div>
I am not hurrying anything.<br>
<br>
Where did you see me saying anything about timeframes ?<br>
The necessary default namespace support is not even there.<br>
<br>
I'm discussing principles, not timeframes.<br>
<br>
And the issue of compatibility: It is a bogus discussion, you know this as well as I do.<br>
If Delphi itself is not compatible between versions, then we cannot do so either, and must choose a version to which we are compatible (2 versions if you accept/count the 1-byte RTL).<br>
<br>
Whether that turns out to be D2009 or DXE1/2/3/4/5: I honestly couldn't care less.<span><font color="#888888"><br>
<br>
Michael.</font></span><div><div><br>
______________________________<u></u>_________________<br>
fpc-pascal maillist - <a href="mailto:fpc-pascal@lists.freepascal.org" target="_blank">fpc-pascal@lists.freepascal.<u></u>org</a><br>
<a href="http://lists.freepascal.org/mailman/listinfo/fpc-pascal" target="_blank">http://lists.freepascal.org/<u></u>mailman/listinfo/fpc-pascal</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
fpc-pascal maillist - <a href="mailto:fpc-pascal@lists.freepascal.org">fpc-pascal@lists.freepascal.org</a><br>
<a href="http://lists.freepascal.org/mailman/listinfo/fpc-pascal" target="_blank">http://lists.freepascal.org/mailman/listinfo/fpc-pascal</a><br></blockquote></div><br></div>