Mailing-List: contact etch-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: etch-dev@incubator.apache.org
Message-ID: <1289227079.1232489819798.JavaMail.jira@brutus>
Date: Tue, 20 Jan 2009 14:16:59 -0800 (PST)
From: "scott comer (JIRA)" <jira@apache.org>
To: etch-dev@incubator.apache.org
Subject: [jira] Created: (ETCH-27) mixins cause trouble when two or more
 mixed in files define a type with the same name.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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


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.