Thread overview | |||||
---|---|---|---|---|---|
|
June 06, 2005 import conflicts are a pain... | ||||
---|---|---|---|---|
| ||||
core/rotozoom.d(26): import core.rotozoom.std conflicts with core.texture.std at core/texture.d(48) and guess what? the problem lies in neither of these files. i had to figure out which file I needed to add another import to, and which import I need to add. It took me way too long as I rarely get this error, but when I do it is really annoying. *sigh* Is it possible for DMD to give at least a little nicer error message, like... core/rotozoom.d(26): import core.rotozoom.std conflicts with core.texture.std at core/texture.d(48), try importing std.math to core/frame.d or core/rotozoom.d(26): import core.rotozoom.std conflicts with core.texture.std at core/texture.d(48), however due to the nature of this error message, the problem lies in neither of the given files, good luck finding it! Especially if you are not the sole developer, and have no clue which file it could possible be. just frusterating... had to rant, sorry. - clayasaurus |
June 06, 2005 Re: import conflicts are a pain... | ||||
---|---|---|---|---|
| ||||
Posted in reply to clayasaurus | clayasaurus wrote: > core/rotozoom.d(26): import core.rotozoom.std conflicts with core.texture.std at core/texture.d(48) > > and guess what? the problem lies in neither of these files. i had to figure out which file I needed to add another import to, and which import I need to add. It took me way too long as I rarely get this error, but when I do it is really annoying. > > *sigh* > > Is it possible for DMD to give at least a little nicer error message, like... > > core/rotozoom.d(26): import core.rotozoom.std conflicts with core.texture.std at core/texture.d(48), try importing std.math to core/frame.d > > or > > core/rotozoom.d(26): import core.rotozoom.std conflicts with core.texture.std at core/texture.d(48), however due to the nature of this error message, the problem lies in neither of the given files, good luck finding it! Especially if you are not the sole developer, and have no clue which file it could possible be. > > > just frusterating... had to rant, sorry. > - clayasaurus I thought those errors were caused by the module name being different than the file name.. like testing/test.d ------------------------ module testing.tester.d ------------------------ is an error, but testing/test.d ------------------------ module testing.test.d ------------------------ or so I have always thought. -- Thanks, Trevor Parscal www.trevorparscal.com trevorparscal@hotmail.com |
June 06, 2005 Re: import conflicts are a pain... | ||||
---|---|---|---|---|
| ||||
Posted in reply to Trevor Parscal | Trevor Parscal wrote:
> clayasaurus wrote:
>
>> core/rotozoom.d(26): import core.rotozoom.std conflicts with core.texture.std at core/texture.d(48)
>>
>> and guess what? the problem lies in neither of these files. i had to figure out which file I needed to add another import to, and which import I need to add. It took me way too long as I rarely get this error, but when I do it is really annoying.
>>
>> *sigh*
>>
>> Is it possible for DMD to give at least a little nicer error message, like...
>>
>> core/rotozoom.d(26): import core.rotozoom.std conflicts with core.texture.std at core/texture.d(48), try importing std.math to core/frame.d
>>
>> or
>>
>> core/rotozoom.d(26): import core.rotozoom.std conflicts with core.texture.std at core/texture.d(48), however due to the nature of this error message, the problem lies in neither of the given files, good luck finding it! Especially if you are not the sole developer, and have no clue which file it could possible be.
>>
>>
>> just frusterating... had to rant, sorry.
>> - clayasaurus
>
> I thought those errors were caused by the module name being different than the file name.. like
>
> testing/test.d
> ------------------------
> module testing.tester.d
> ------------------------
>
> is an error, but
>
> testing/test.d
> ------------------------
> module testing.test.d
> ------------------------
>
> or so I have always thought.
>
no, that's another one that is annoying the first time but after that you realize what is wrong.
"module core.tex is in multiple packages core.tex"
when core.tex should be named core.texture.
maybe the message should be...
"module core.tex module name does not match filename"
anyway, just search the bugs forum for
"import std conflicts with d.std"
to know what I am talking about. not sure how i can post a link to it.
|
Copyright © 1999-2021 by the D Language Foundation