From: Michael Edgar <adgar@...>
Date: 2011-09-02T10:57:00+09:00
Subject: Re: ripper on array access operation

--Apple-Mail=_EB35004E-9B1F-4EDB-A0FA-9EB361877069
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On Sep 1, 2011, at 9:37 PM, Justin Collins wrote:

> For what I use it for, I don't care about the exact syntax used when =
they mean the same thing, and the fewer node types I need to check for, =
the better.

I suspect this is actually only true at the margins, which is why parse =
trees are valuable and why I argue the corners RubyParser cuts are =
arbitrary and silly.

Would you prefer that RubyParser turn "@foo =3D bar" into a call to =
"instance_variable_set"?

Or "class A < B; end" into a series of conditions, constant lookups, =
assignments, "Class.new(B)", and so on?

Should "class << foo; end" turn into "foo.singleton_class.class_eval =
do.. end"?

Michael Edgar
adgar@carboni.ca
http://carboni.ca/


--Apple-Mail=_EB35004E-9B1F-4EDB-A0FA-9EB361877069--