generate Orc types for Java "class" sites

[GoogleCodeExporter]

When the user writes:
class Foo = ...

this should make Foo available as a type name, and ensure that it
corresponds to the appropriate type for type checking purposes.

Original issue reported on code.google.com by adrianqu...@gmail.com on 18 Apr 2009 at 4:03

[GoogleCodeExporter]

It looks like changes related to this issue are breaking the conversion from
orc.ast.oil to orc.ast.oil.xml.

There should be a mapping between orc.ast.oil.xml.type.ClassnameType and some
class(es) in orc.type, implemented in one direction by
orc.ast.oil.xml.type.ClassnameType#unmarshal(Config) and in the other direction 
by
orc.type.Type#marshal(). The Type#marshal() method is missing so the conversion 
only
works one way.  The most straightforward way to do this is to introduce a simple
wrapper for class types along the same lines as orc.type.SiteType
(orc.type.ClassnameType was intended to serve this role).

As a workaround until this is fixed, I am disabling the Java type-checking 
feature by
changing orc.ast.simple.type.ClassnameType to return a dummy 
orc.type.ClassnameType.

Original comment by adrianqu...@gmail.com on 9 Jun 2009 at 5:22

• Added labels: Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Instantiation of class types is now part of the typechecking process, rather 
than part of the translation to OIL. OIL 
now contains only syntactic representations of types, so this is no longer an 
issue.

Original comment by dkitc...@gmail.com on 3 Sep 2009 at 7:58

• Changed state: Fixed