Thread overview
static import is in multiple defined
Mar 02, 2008
Saaa
Mar 02, 2008
Saaa
Mar 02, 2008
Saaa
Mar 02, 2008
Jesse Phillips
Mar 02, 2008
Saaa
Mar 02, 2008
Saaa
Mar 02, 2008
Saaa
March 02, 2008
My projects are starting to grow and I really need to start using packages :)

So I moved my userEvents module to user.events.
But when I do..

static import user.events;

..I get : module events is in multiple defined.

Does this mean that 'events' needs to be unique even though I use it statically and thus can only access it through user.events?


March 02, 2008
Erm, changing the name to events2 results in the same error. I must be doing something wrong :/


March 02, 2008
"Saaa" <empty@needmail.com> wrote in message news:fqdfj4$1ss2$1@digitalmars.com...
> My projects are starting to grow and I really need to start using packages :)
>
> So I moved my userEvents module to user.events.
> But when I do..
>
> static import user.events;
>
> ..I get : module events is in multiple defined.
>
> Does this mean that 'events' needs to be unique even though I use it statically and thus can only access it through user.events?
>

Does the module declaration at the tope of user.events say "module user.events;"?

DMDFE's errors for imports and modules are absolutely *impenetrable*.  This one error message maps to several possible causes, none of which are obvious from what it (rather ungrammatically) says.


March 02, 2008
> Does the module declaration at the tope of user.events say "module user.events;"?

No, I put events.d in 'user' dir.

>
> DMDFE's errors for imports and modules are absolutely *impenetrable*. This one error message maps to several possible causes, none of which are obvious from what it (rather ungrammatically) says.
 handy :)


March 02, 2008
On Sun, 02 Mar 2008 08:26:48 +0100, Saaa wrote:

>> Does the module declaration at the tope of user.events say "module user.events;"?
> 
> No, I put events.d in 'user' dir.
> 
> 
>> DMDFE's errors for imports and modules are absolutely *impenetrable*. This one error message maps to several possible causes, none of which are obvious from what it (rather ungrammatically) says.
>  handy :)

you need to have module user.events; in you events.d file or it will not work.
March 02, 2008
Ok, I thought that putting it in a folder would be enough :/ Thanks

>
> you need to have module user.events; in you events.d file or it will not work.


March 02, 2008
>
> you need to have module user.events; in you events.d file or it will not work.

module user.events is in multiple packages user.events.

What else am I doing wrong?


March 02, 2008
Ignore that. My bad

>
> module user.events is in multiple packages user.events.
>
> What else am I doing wrong?
>