--fNt3LaeWOiqzgRAPbN+
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Fri, 2005-12-09 at 10:11 +0900, Steve Litt wrote:
> Is there any chance of a Ruby change so as not to require the paren to be 
> flush up against the function name?

Egh... I think that'd introduce more ambiguities into the grammar...
it's pretty bad that way already.

-mental

--fNt3LaeWOiqzgRAPbN+
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBDmSXrcUNIGiXCc4MRAm9PAJoDQrag9cb9RCLTGy5WwrYyuuxR8gCgr9FE
oFnJfon4c3JZ5685nCJpDqw/h
-----END PGP SIGNATURE-----

--fNt3LaeWOiqzgRAPbN+--