Modules/packages and cryptic errors

Frank Benoit keinfarbton at googlemail.com
Sat Oct 31 07:19:02 PDT 2009


al schrieb:
> Frank Benoit Wrote:
> 
>> al schrieb:
>>> module bar is in multiple defined
>> This often indicates a modules file name and the identifier in the
>> "module" statement are unequal (case sensitivity)
> 
> I have all files and imports lowercase. I have class names following filenames capitalized, but that shouldn't matter, should it?
> 
> 
> When I run:
> 
> dmd foo/bar.d
> 
> is that assuming module foo.bar or bar? If that's the latter, it might explain why I'm getting an error (import finds this file under foo.bar), but how should I compile files then?
> 
> 

if 'foo' shall be package, in bar.d there should be "module foo.bar;".
If imported from somewhere else, it should be "import foo.bar;".

Class/Type names should not matter.


More information about the Digitalmars-d-learn mailing list