On Wed, Jun 27, 2018 at 11:51 AM, Sven Barth via fpc-devel
wrote:
> Marcos Douglas B. Santos schrieb am Mi., 27. Juni 2018,
> 14:37:
>>
>> Sven and all,
>> Is there any change to implement this?
>
>
> Not from me. I don't care about that.
Thanks for your sincerity.
Regards,
Marcos Douglas
_
Marcos Douglas B. Santos schrieb am Mi., 27. Juni 2018,
14:37:
> Sven and all,
> Is there any change to implement this?
>
Not from me. I don't care about that.
Regards,
Sven
>
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.fre
Sven and all,
Is there any change to implement this?
Thanks.
Best regards,
Marcos Douglas
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
On Sun, Jun 24, 2018 at 5:49 PM, Marcos Douglas B. Santos
wrote:
> Instead, I prefer using fully qualified names and just adjust in some
> contexts that *there is* already a conflict name.
> In other words, `uses foo as bar;` will be use per unit. It is not to
> intent "renaming" a unit name for a
On Sun, Jun 24, 2018 at 4:06 PM, Sven Barth via fpc-devel
wrote:
> Am 24.06.2018 um 16:49 schrieb Marcos Douglas B. Santos:
>>
>> Hypothetically, let's suppose that Windows and Graphics unit belongs
>> to `FPC.RTL.` namespace, a "long name".
>> Using a syntax sugar to macros, I propose to implemen
Am 24.06.2018 um 16:49 schrieb Marcos Douglas B. Santos:
Hypothetically, let's suppose that Windows and Graphics unit belongs
to `FPC.RTL.` namespace, a "long name".
Using a syntax sugar to macros, I propose to implement the "as"
keyword in units declarations:
=== code begin ===
uses
FPC.RTL
In another thread[1] Sven Barth explained to me how to use macros
properly following my example before.
However, I think this could be used as a syntax sugar for unit aliases
on the code — not about paths.
Graeme and me have already proposed[2] this years ago. I am against to
include more features
