Import concerns revisited

Jari-Matti Mäkelä jmjmak at utu.fi.invalid
Fri Jul 14 15:53:29 PDT 2006


John Reimer wrote:
> On Fri, 14 Jul 2006 11:54:53 -0700, Jari-Matti Mäkelä
> <jmjmak at utu.fi.invalid> wrote:
> 
>> Jari-Matti Mäkelä wrote:
>>> Although I don't think anyone particularly was suggesting that it should
>>> be a default. According to
>>> <http://www.prowiki.org/wiki4d/wiki.cgi?ImportConflictResolution> a
>>> majority of active members only want to extend the import syntax so that
>>> old programs would work exactly as they do now and new programs would
>>> have better control over their namespaces. The 'static import' + some
>>> aliasing would be more than enough to fix this but many coders are so
>>> lazy (including me) they want import to support aliasing directly. ;)
>>
>> I have to admit that 'static import' syntax has one advantage over #4 on
>> that wiki. No-one has come up yet with an elegant way to provide only
>> FQN access with the 'as'-syntax. Can't we have both. :)
>>
> 
> 
> Really?
> 
> import spec.lib.spec as spec.lib.spec;
> 
> Doesn't that work for you?

Of course :)



More information about the Digitalmars-d mailing list