On Tue, Oct 11, 2016 at 7:21 AM, Santiago A. <s...@ciberpiula.net> wrote:
> My two cents:
>
> Whenever there is a conflict, an ambiguity, you must full qualify the
> identifier otherwise the compiler will complain.
> For the special cases, when you need to hide the declaration, you could
> use the directive "override" for global declarations (types, functions,
> procedures, const, vars) , so the compiler knows that it must ignore
> previous declaration if the identifier is not full qualified. Just like
> it does now.
>
> For compatibility issues, you could add a compiler check, i.e.
> {$CHECK_AMBIGUITY ON/OFF}You're, indeed that's a good idea. But what I do, for years, is import my units using an order by priority, for example: <fpc units> <laz units> <3rd units> <my libs units> <my domain units> ...and so on. The compiler will give me the identifier from below to above. Best regards, Marcos Douglas _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
