2011/10/18 Carter Cheng <cartercheng / gmail.com>:
> bytecode support(does this mean the newer versions of ruby will support
> fixed bytecodes or will bytecodes be inspectable via the ruby system itse=
lf)

Ruby 1.9 uses a VM (a.k.a. YARV).
A given script is parsed and compiled as a bytecode, and runs with the VM.

"Bytecode export" means to support exporting the bytecode, and import
and run the bytecode.
It reduces the parse phase and compile phase.

Bytecode inspectation, dissembler for the Ruby VM, is already bundled:
% ruby -e'puts RubyVM::InstructionSequence.compile(%q[p 1+2]).disasm'
=3D=3D disasm: <RubyVM::InstructionSequence:<compiled>@<compiled>>=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
0000 trace            1                                               (   1=
)
0002 putnil
0003 putobject        1
0005 putobject        2
0007 opt_plus         <ic:2>
0009 send             :p, 1, nil, 8, <ic:1>
0015 leave

> 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 capabil=
ity?)

A Ruby interpreter parses a given script and makes a syntax tree,
but users can't access the tree through a public API.
This means adding such public API.

> is the current proposal for the gc API a C level api?

C level.
http://redmine.ruby-lang.org/issues/4990

--=20
NARUSE, Yui =A0<naruse / airemix.jp>