On Dec 12, 2010, at 16:28 , Urabe Shyouhei wrote:

> (2010/12/13 9:06), Ryan Davis wrote:
>> Providing a standard AST definition for consumers !=3D defining the =
internals.=20
>=20
> Definitely.  I'm not against a standardised AST itself; just in doubt =
for that
> standard to touch MRI internals.  To make a live AST access possible =
more or
> less new API is mandatory.  The sadness is almost every new feature =
added to
> MRI are seen as Ruby standard these days; we do not want that.
>=20

That's fair... tho in this case I know that rubinius and jruby would =
throw in support fairly quickly and would probably welcome it as a =
standard feature.