[ETCH-27] mixins cause trouble when two or more mixed in files define a type with the same name.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.1
• Fix Version/s: 1.0.2
• Component/s: binding-csharp, binding-java, compiler
• Assignee: Robert Scott Comer
• Reporter: Robert Scott Comer
• Created: 20/Jan/09 22:16
• Updated: 26/Sep/13 08:31
• Resolved: 26/Jan/09 17:56

Description

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.