Ant wrote:

> In article <borasn$271q$2@digitaldaemon.com>, Walter says...
> 
>>
>>"Ant" <Ant_member@pathlink.com> wrote in message
>>news:bon0e7$1tkm$1@digitaldaemon.com...
>>
>>>This is the kind of things Walter would wants to know about so
>>>he can corrected them.
>>>Will you make a "BUG:" post or should I?
>>
>>Yes, I do want to know about them. What would be real nice is a short
>>example illustrating the problem (either a bug, bad error message, etc.).
>>
>>
> 
> 
> This one is easy to illustrate.
> I'll do it tonight.
> 
> Ant
> 
> 
I've already written an example.  I just posted it in a new thread called "BUG: multiple packages".

Justin

"Ant" <Ant_member@pathlink.com> wrote in message news:borc64$29an$1@digitaldaemon.com...
> This one is easy to illustrate.
> I'll do it tonight.

I've found a problem, it might be the cause of what's ailing dui. Several of
the modules need a module statement, i.e. string.d needs the line:
    module std.string;
in it.

In article <bosndb$1cvi$1@digitaldaemon.com>, Walter says...
>
>
>"Ant" <Ant_member@pathlink.com> wrote in message news:borc64$29an$1@digitaldaemon.com...
>> This one is easy to illustrate.
>> I'll do it tonight.
>
>I've found a problem, it might be the cause of what's ailing dui. Several of the modules need a module statement, i.e. string.d needs the line:
>    module std.string;
>in it.

I wouldn't be surprised. That might be it!
I should have tought of this,
I believe had similar problems before...
(I'm "almost" mad at me...)

I can add all the missing module declarations
and try it (tonight).

Should module be mandatory? (as in java)
Or can the compiler give a more clear message? - that will
make this problem easy to detect.
Otherwise this will happen again.

Ant

"Ant" <Ant_member@pathlink.com> wrote in message news:botfkf$2i01$1@digitaldaemon.com...
> Should module be mandatory? (as in java)

I've been reluctant to do that, as skipping the module statement makes writing trivial D programs even easier <g>.

> Or can the compiler give a more clear message? - that will
> make this problem easy to detect.
> Otherwise this will happen again.

I think better error messages are the ticket here.

In article <botfkf$2i01$1@digitaldaemon.com>, Ant says...
>
>In article <bosndb$1cvi$1@digitaldaemon.com>, Walter says...
>>
>>
>>"Ant" <Ant_member@pathlink.com> wrote in message news:borc64$29an$1@digitaldaemon.com...
>>> This one is easy to illustrate.
>>> I'll do it tonight.
>>
>>I've found a problem, it might be the cause of what's ailing dui. Several of the modules need a module statement, i.e. string.d needs the line:
>>    module std.string;
>>in it.
>
>I can add all the missing module declarations
>and try it (tonight).

did not work... but I didn't have much time to do it.
I'll recheck it.

I did add all module declarations (except ti_*),
change all import to private (on phobos, and DUI) (except ti_*).

Any hints beside checking every thing was done properly, and change ti_* files?

Ant