[e-lang] translating one objcaps language to another?

[John Carlson]

The only think I can think of is that the methods might be declared in  
different places.
For example, Java might implement things in a concrete class when  
inheriting from an interface, and JavaScript would either reference  
the interface's method, or copy the interface's method.  I think you  
would need to verify that the semantics remained the same in your  
inheritance graphs.

I think that JavaScript can emulate Java class derivation and Java can  
emulate JavaScript (ala Rhino).

You need to think about prototype versus archetype inheritance.

John
On Jan 22, 2008, at 12:18 PM, Lex Spoon wrote:

> Does anyone know of a compiler that goes from one object capabilities
> language to another?  If you were working with such a tool, what you
> would want is to be able to reason in either the source language or
> the target language and not go wrong.  I would like to better
> understand what exactly this level-shifting means.
>
> It looks tempting to say you want object graphs in the source
> language to map to object graphs in the target language.  If the
> source language has a reference from SA to SB, then you want the
> target language to have a reference from TA to TB where TA and TB are
> the objects corresponding to SA and SB.  Given this property, it
> would seem like you could shift your reasoning between the
> compilation levels pretty safely.
>
> I am not sure, though.  What do you guys think?
>
> -Lex
>
> _______________________________________________
> e-lang mailing list
> e-lang at mail.eros-os.org
> http://www.eros-os.org/mailman/listinfo/e-lang