I applied this patch on my dev machine and tried using the build result to compile some etch files - the problem described with this issue was gone - i'm happy with this fix.
--Wei On Tue, Jan 20, 2009 at 4:59 PM, scott comer (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/ETCH-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] > > scott comer updated ETCH-27: > ---------------------------- > > Attachment: patch.txt > > file version of the patch. tested. > > > mixins cause trouble when two or more mixed in files define a type with > the same name. > > > -------------------------------------------------------------------------------------- > > > > Key: ETCH-27 > > URL: https://issues.apache.org/jira/browse/ETCH-27 > > Project: Etch > > Issue Type: Bug > > Components: compiler, csharp-binding, java-binding > > Affects Versions: 1.0.1 > > Reporter: scott comer > > Assignee: scott comer > > Attachments: patch.txt > > > > > > three etch files, Foo.etch, Bar.etch, Baz.etch. > > Foo mixes in Bar and Baz. > > Bar and Baz each define a struct Entry ( int x ). > > Bar defines a message void barGet( Entry e ) > > Baz defines a message void bazGet( Entry e ) > > when you compile Foo the compiler fails because it conducts it search for > type Entry from the top down instead of the bottom up. a top down search > finds two definitions for Entry. the reference is ambigous and therefore not > allowed. > > a bottom up search guarantees that barGet binds to Bar's Entry and bazGet > binds to Baz's Entry. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > >
