View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0000007 | mercury | Bug | public | 2007-09-27 23:53 | 2007-10-26 15:48 | ||||||||
Reporter | anonymous | ||||||||||||
Assigned To | |||||||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||||||
Status | feedback | Resolution | open | ||||||||||
Product Version | |||||||||||||
Target Version | Fixed in Version | ||||||||||||
Summary | 0000007: Type ctor module name bug | ||||||||||||
Description | Date: Wed, 1 Aug 2007 17:45:29 +1000 From: Ralph Becket <rafe@csse.unimelb.edu.au> To: Julien Fischer <juliensf@csse.unimelb.edu.au> Subject: Type ctor module name bug Unpack the attached tar file and build and run foo1 and foo2. They give different answers, which I think is wrong. -- Ralph | ||||||||||||
Tags | No tags attached. | ||||||||||||
Attached Files |
|
Notes | |
juliensf (administrator) 2007-10-26 15:48 |
The problem is that in the program `foo2' it is ambiguous as to whether the file bar.m contains the module `bar' or the module `foo2.bar'. The compiler apparently decides that it contains both! I think the best thing to do here would be to emit a warning if the module -> source file map is not a bijection. |