Global Imports in DMD not working?

[Chris Nicholson-Sauls]

Hasan Aljudy wrote:
> Trevor Parscal wrote:
>> I've been getting annoyed with this lately...
>>
>> a imports b, which imports c, but a still can't access anything in c...
>>
>> Anybody else notice this?
>>
>> I'm using dmd 1.0
> 
> imports are private by default, i.e. they don't propogate.
> use public imports, i.e. in b, say:
> public import c;
> this way, any module that imports b automatically imports c.

Actually I was just about to post about this, as my Bovis project has several uses of 
public imports...  For some unknown reason, DMD/1.00 is not honoring public imports. 
Given Trevor's case: a imports b, which /publicly/ imports c, but a cannot see c.

It doesn't seem to /always/ happen though, and I've yet to find a pattern in it.

-- Chris Nicholson-Sauls