OSM issue

Guido Chari charig at gmail.com
Tue Aug 11 20:15:44 UTC 2015

Well that is a little confusing for me. Most of the classes ending with
impl like DynamicObjectImpl and LayoutImpl are abstract and there are
subclasses with standard implementations (BasicLayout, DynamicObjectBasic).
I thought those implementations were the ones used for JRuby.
If i would like a different scheme of fields for my dynamicObject i thought
the standard way was to subclass DynamicObjectImpl. If this is not the way,
what is the suggested way of using the framework for defining my own
dynamic object with different count of primitive and object fields?

2015-08-11 16:38 GMT-03:00 Andreas Woess <andreas.woess at oracle.com>:

> Not sure I follow. Building on top of the implementation classes
> (LayoutImpl, LayoutStrategy, etc.) is not supported (and most likely
> never will be), if that's what you're trying to do.
> Otherwise, you can easily create a new Layout using LayoutBuilder or the
> convenience Layout.createLayout() method.
> - andreas
> On 2015-08-11 21:26, Guido Chari wrote:
> > Hi,
> >
> > While implementing an object model based on the OSM provided by Truffle
> (i
> > followed the JRuby implementation) i have faced with a problem.
> >
> > Mainly, for creating a new Layout i need a LayoutStrategy. I would like
> to
> > use the DefaultStrategy but it is not visible from outside the package, I
> > think all other "defaults" are declared public. Am i missing something or
> > DefaultStrategy should be public too?
> >
> > Best,
> > Guido.
> >

More information about the graal-dev mailing list