[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ruby-core
Subject:    [ruby-core:33716] Re: Towards a standardized AST for Ruby code
From:       Rocky Bernstein <rockyb () rubyforge ! org>
Date:       2010-12-14 12:10:55
Message-ID: AANLkTikBOGR=NcrNE6HPdSS_BC8WaOefb9JHXPSCe=0c () mail ! gmail ! com
[Download RAW message or body]

On Tue, Dec 14, 2010 at 3:58 AM, Charles Oliver Nutter
<headius@headius.com>wrote:

> On Sun, Dec 12, 2010 at 6:34 PM, Rocky Bernstein <rockyb@rubyforge.org>
> wrote:
> > On  the other hand, I do believe that in the rubinius implementation it
> is
> > possible to have one interpreter/system which suits both competing needs
> of
> > performance and live introspection. I believe this because in a sense
> > rubinius *is* already two implementations: a Ruby interpreter plus a JIT
> for
> > it.
>
> JRuby has also been a mixed-mode implementation since early 2008.
> Depending on what information you want available for debugging, it's
> possible to provide it in interpreted mode; but as we discussed at
> RubyKaigi, all optimizing compilers will eventually want to throw away
> information about code that isn't necessary for execution, and then
> you have to do debugging only with the interpreter (or with a compiler
> that doesn't do those optimizations, which may be fine). I don't think
> you currently want/need anything we throw away, but we need to be
> mindful of that possibility.
>
> - Charlie
>

Thanks for the information. Yes I suspect it does, but I need to check and
get back to you. it's on my list of things to do.

And thanks for your mindfulness.

[Attachment #3 (text/html)]

<br><br><div class="gmail_quote">On Tue, Dec 14, 2010 at 3:58 AM, Charles Oliver \
Nutter <span dir="ltr">&lt;<a \
href="mailto:headius@headius.com">headius@headius.com</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;"> <div class="im">On Sun, Dec 12, 2010 at 6:34 PM, Rocky \
Bernstein &lt;<a href="mailto:rockyb@rubyforge.org">rockyb@rubyforge.org</a>&gt; \
wrote:<br> &gt; On  the other hand, I do believe that in the rubinius implementation \
it is<br> &gt; possible to have one interpreter/system which suits both competing \
needs of<br> &gt; performance and live introspection. I believe this because in a \
sense<br> &gt; rubinius *is* already two implementations: a Ruby interpreter plus a \
JIT for<br> &gt; it.<br>
<br>
</div>JRuby has also been a mixed-mode implementation since early 2008.<br>
Depending on what information you want available for debugging, it&#39;s<br>
possible to provide it in interpreted mode; but as we discussed at<br>
RubyKaigi, all optimizing compilers will eventually want to throw away<br>
information about code that isn&#39;t necessary for execution, and then<br>
you have to do debugging only with the interpreter (or with a compiler<br>
that doesn&#39;t do those optimizations, which may be fine). I don&#39;t think<br>
you currently want/need anything we throw away, but we need to be<br>
mindful of that possibility.<br>
<br>
- Charlie<br></blockquote><div><br></div><div>Thanks for the information. Yes I \
suspect it does, but I need to check and get back to you. it&#39;s on my list of \
things to do. </div><div><br></div><div>And thanks for your mindfulness.  </div> \
</div><br>



[prev in list] [next in list] [prev in thread] [next in thread]