<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 13.09.2017 10:44, Michael Van
Canneyt via Lazarus wrote:<br>
</div>
<blockquote type="cite"
cite="mid:alpine.DEB.2.20.1709131014090.11060@home.telenet.be"><br>
On Wed, 13 Sep 2017, Graeme Geldenhuys via Lazarus wrote:
<br>
<br>
<blockquote type="cite" style="color: #000000;">On 2017-09-12
19:01, Alexey via Lazarus wrote:
<br>
<blockquote type="cite" style="color: #000000;">It is new.
Please rename (it's easy for new component) all files:
<br>
usually its good with one prefix. E.g. fprep_*.*.
<br>
</blockquote>
<br>
hahaha... I had the units like that, using underscores. eg:
fpreport_export_aggpas.pas, fpreport_export_fpimage.pas etc.
Michael didn't like it, so it got renamed before it went into
FPC Trunk. :)
<br>
<br>
The LCL related units could be prefixed though, as Michael
mentioned.
<br>
</blockquote>
<br>
They should be, since some of the names used in the designer are
indeed too
<br>
generic.
<br>
<br>
<blockquote type="cite" style="color: #000000;">Then again, maybe
it's time FPC starts making use of namespaces and dotted unit
names? Just a thought. In Delphi it is actually pretty useful
and also stops unit name conflicts. FPC does need a bit more
work though to fully support namespaces - at least the way
Delphi uses it.
<br>
</blockquote>
<br>
As long as there are no command-line switch and directive for
setting namespaces, they are completely useless. And even with
them, the benefit is
<br>
doubtful.
<br>
<br>
The benefit of writing fpreport.exporthtml versus
fpreportexporthtml is zero.
</blockquote>
<p>You forgot one thing: third-party libraries. E.g. your fpReport
could use the "fprep" namespace. In the fpReport package you then
define to use the fprep namespace - it means you can use units in
fpReport without the "fprep" namespace - and without any
collisions.<br>
</p>
<p>In the main application you have the choice if you want to add
the fprep namespace and can use fpReport units without the
namespace or not. Collisions have to be resolved with the
namespace anyway - but this is no really drawback.</p>
<p>Furthermore code tools can handle dotted units (I added the
support :) ) and namespaces will be handled as well once FPC
supports them.</p>
<p>So yes, namespaces are good :) - or at least they are no harm.
It's your decision not to use them - they won't break anything.<br>
</p>
<p>Ondrej<br>
</p>
</body>
</html>