www.digitalmars.com Home | Search | C & C++ | D | DMDScript | News Groups | index | prev | next
Archives

D Programming
D
D.gnu
digitalmars.D
digitalmars.D.bugs
digitalmars.D.dtl
digitalmars.D.ide
digitalmars.D.dwt
digitalmars.D.announce
digitalmars.D.learn
digitalmars.D.debugger

C/C++ Programming
c++
c++.announce
c++.atl
c++.beta
c++.chat
c++.command-line
c++.dos
c++.dos.16-bits
c++.dos.32-bits
c++.idde
c++.mfc
c++.rtl
c++.stl
c++.stl.hp
c++.stl.port
c++.stl.sgi
c++.stlsoft
c++.windows
c++.windows.16-bits
c++.windows.32-bits
c++.wxwindows

digitalmars.empire
digitalmars.DMDScript
electronics




digitalmars.D.bugs - [Issue 2059] New: Horrible error message

↑ ↓ ← d-bugmail puremagic.com writes:
http://d.puremagic.com/issues/show_bug.cgi?id=2059

           Summary: Horrible error message
           Product: D
           Version: 1.027
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DMD
        AssignedTo: bugzilla digitalmars.com
        ReportedBy: jason.james.house gmail.com


file(line): module XXX is in multiple defined

I got this message when importing a file that lacked a module declaration at
the top.  Please make the error message more readable.


-- 
Apr 29 2008
↑ ↓ → d-bugmail puremagic.com writes:
http://d.puremagic.com/issues/show_bug.cgi?id=2059





------- Comment #1 from technocrat7 gmail.com  2008-05-01 08:45 -------
I've seen this error before myself, and I never found it very helpful (I don't
remember exactly what the code looked like, though). 

We should probably include a short example of what code produces this message.
I'm guessing it's something like this:

// file 1: pack/module1.d
import pack.module2;

//file 2: pack/module2.d
import pack.module1;

(from
http://www.digitalmars.com/d/archives/digitalmars/D/learn/Module_is_in_multiple_defined_7756.html)

Another related thread:
http://www.digitalmars.com/d/archives/digitalmars/D/learn/static_import_is_in_multiple_defined_11474.html

Also, it might be good to provide a suggestion for what the error message
should be (if it actually should be an error), but I don't really understand
what the message should be.


-- 
May 01 2008