API Visibility was: Segfault when running compiled Truffle method.
Christian Humer
christian.humer at gmail.com
Thu Jan 23 09:27:55 PST 2014
We need a module system ;-).
- Christian Humer
On Thu, Jan 23, 2014 at 6:26 PM, Andreas Woess <andreas.woess at jku.at> wrote:
> FWIW, one would have to reduce visibility of the DefaultTruffleRuntime
> as well (although that is not as prone to misuse) but that means moving
> classes around.
>
> - andreas
>
> On 23.01.2014 18:25, Christian Wimmer wrote:
> > I'll give it a try, since I'm playing around with that code anyway
> > right now.
> >
> > -Christian
> >
> >
> > On 01/23/2014 09:18 AM, Andreas Woess wrote:
> >> Yes. I've just checked -- it should be fine to reduce visibility of the
> >> DefaultVirtualFrame constructor and class. If anyone uses them, they
> >> should migrate.
> >>
> >> - andreas
> >>
> >> On 23.01.2014 18:14, Christian Wimmer wrote:
> >>>> In general, never create frames yourself, always use the methods in
> >>>> TruffleRuntime (there's also one for virtual frames nowadays,
> >>>> should you
> >>>> need it).
> >>>
> >>> That leads to the question: why are the classes and constructors
> >>> public?
> >>>
> >>> Can I reduce the visibility without breaking any existing languages?
> >>>
> >>> -Christian
> >>>
>
>
> ---
> This email is free from viruses and malware because avast! Antivirus
> protection is active.
> http://www.avast.com
>
>
More information about the graal-dev
mailing list