From: Carter Cheng <cartercheng@...>
Date: 2011-10-18T03:30:37+09:00
Subject: [ruby-core:40184] Re: plans for 2.0.

--20cf30780d9e697db304af82cd53
Content-Type: text/plain; charset=ISO-8859-1

I skimmed over the whole thread I am curious about certain details here-

bytecode support(does this mean the newer versions of ruby will support
fixed bytecodes or will bytecodes be inspectable via the ruby system itself)
parse trees(it would seem that the current system does have some sort of
parse tree system- so does this also mean some sort of inspection
capability?)
is the current proposal for the gc API a C level api?

Thanks in advance,

Carter.

On Tue, Oct 18, 2011 at 5:14 AM, Carter Cheng <cartercheng@gmail.com> wrote:

> Thanks.
>
>
> On Mon, Oct 17, 2011 at 7:47 PM, NARUSE, Yui <naruse@airemix.jp> wrote:
>
>> 2011/10/17 Carter Cheng <cartercheng@gmail.com>:
>> > I am curious if there are some discussion for the plans leading up to
>> 2.0
>> > (feature wise). I am somewhat interested in ruby internals and I was a
>> > little curious if there are details wrt to what directions ruby will
>> take in
>> > the future and how these details might potentially change.
>>
>> See the thread from [ruby-core:39810].
>> http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/39810.
>>
>> --
>> NARUSE, Yui  <naruse@airemix.jp>
>>
>>
>

--20cf30780d9e697db304af82cd53
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I skimmed over the whole thread I am curious about certain details here-<di=
v><br></div><div>bytecode support(does this mean the newer versions of ruby=
 will support fixed bytecodes or will bytecodes be inspectable via the ruby=
 system itself)</div>
<div>parse trees(it would seem that the current system does have some sort =
of parse tree system- so does this also mean some sort of inspection capabi=
lity?)</div><div>is the current proposal for the gc API a C level api?</div=
>
<div><br></div><div>Thanks in advance,</div><div><br></div><div>Carter.</di=
v><div><br><div class=3D"gmail_quote">On Tue, Oct 18, 2011 at 5:14 AM, Cart=
er Cheng <span dir=3D"ltr">&lt;<a href=3D"mailto:cartercheng@gmail.com">car=
tercheng@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Thanks.<div><div></div><div class=3D"h5"><b=
r><br><div class=3D"gmail_quote">On Mon, Oct 17, 2011 at 7:47 PM, NARUSE, Y=
ui <span dir=3D"ltr">&lt;<a href=3D"mailto:naruse@airemix.jp" target=3D"_bl=
ank">naruse@airemix.jp</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
2011/10/17 Carter Cheng &lt;<a href=3D"mailto:cartercheng@gmail.com" target=
=3D"_blank">cartercheng@gmail.com</a>&gt;:<br>
<div>&gt; I am curious if there are some discussion for the plans leading u=
p to 2.0<br>
&gt; (feature wise). I am somewhat interested in ruby internals and I was a=
<br>
&gt; little curious if there are details wrt to what directions ruby will t=
ake in<br>
&gt; the future and how these details might potentially change.<br>
<br>
</div>See the thread from [ruby-core:39810].<br>
<a href=3D"http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/3981=
0" target=3D"_blank">http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby=
-core/39810</a>.<br>
<font color=3D"#888888"><br>
--<br>
NARUSE, Yui =A0&lt;<a href=3D"mailto:naruse@airemix.jp" target=3D"_blank">n=
aruse@airemix.jp</a>&gt;<br>
<br>
</font></blockquote></div><br>
</div></div></blockquote></div><br></div>

--20cf30780d9e697db304af82cd53--