[fpc-devel] Namespaces like URLs
fpc at mfriebe.de
Tue Jul 27 03:14:33 CEST 2010
On 27/07/2010 01:48, Adem wrote:
> On 2010-07-27 1:08 AM, Graeme Geldenhuys wrote:
>> 2010/7/27 Adem :
>>> I wouldn't have much of an issue with something like
>>> zip IN '/units/my/zip.pas' AS myzip;
>>> zip IN '/units/lib/zip/zip.pas' AS ziplib;
>> And if you have multiple developers working on the same project and
>> their source code directory hierarchy is not exactly the same as yours
>> (shown above), then that project would not compile on there systems.
>> You cannot hard-code such paths inside a unit and have any hope that
>> it will be "portable" between developers and OSes (\ vs / delimiters).
> And, it seem you did not read the rest of my post (including the first
> one with this subject line) :)
I am with Graeme on this one, as in I do not see what you may have
written, that solved the above....
To be sure: this mail ?:
where does it solve that if I write a unit with this lazarus namespace
will work on a default windows install; not to speak a linux system. The
path depends on the system.
If you mean the path, is only a string or placeholder, and does not
actually point to the sources (which I can not find in your mail), then
how does fpc know the correct path to the source? (I have 4 lazarus
instalations, and 3 fpc installations => with different versions => how
is fpc going to work that out?
More information about the fpc-devel