On Sat, Nov 2, 2013 at 12:19 PM, Marcos Douglas wrote:
> On Sat, Nov 2, 2013 at 12:32 PM, Dmitry Boyarintsev
> wrote:
> >
> > On Sat, Nov 2, 2013 at 6:55 AM, Marcos Douglas wrote:
>
This works only if you don't want use StrUtils of your project and,
> IMHO, this is more complex solution. You wi
On Sat, Nov 2, 2013 at 7:44 PM, Dmitry Boyarintsev
wrote:
> On Sat, Nov 2, 2013 at 12:19 PM, Marcos Douglas wrote:
>>
>> > compiling with
>> > fpc -ALIAS /lib/* TheLib
>> >
>> > won't help, unless you change "ExtraUtils.pas" to use TheLib.StrUtils
>>
>> Well, is more common to use just ppu files
On Sat, Nov 2, 2013 at 12:19 PM, Marcos Douglas wrote:
> > compiling with
> > fpc -ALIAS /lib/* TheLib
> >
> > won't help, unless you change "ExtraUtils.pas" to use TheLib.StrUtils
>
> Well, is more common to use just ppu files to not compile these files
> every compilation. So, the Lib was alrea
On Sat, Nov 2, 2013 at 12:32 PM, Dmitry Boyarintsev
wrote:
>
> On Sat, Nov 2, 2013 at 6:55 AM, Marcos Douglas wrote:
>>
>> On Fri, Nov 1, 2013 at 11:54 PM, Dmitry Boyarintsev
>> wrote:
>> > Technical problem:
>> > * a unit name collision of two independent library code. Either library
>> > are
>
Hmm, let me extend your example:
/project/unit1.pas
/project/StrUtils.pas
/lib/StrUtils.pas
/lib/ExtraUtils.pas
---code---
unit ExtraUtils;
uses StrUtils; // assumed library StrUtils, not project
===code===
However, since StrUtils is present in project directory, it will be used
instead, causin
On Fri, Nov 1, 2013 at 11:54 PM, Dmitry Boyarintsev
wrote:
> Technical problem:
> * a unit name collision of two independent library code. Either library are
> using unit with the same name. The code in the conflicting units is
> different. Thus one library should use its own unit, the other shoul
