From: Martin Man <Martin.Man@...>
Date: 2002-02-16T20:59:52+09:00
Subject: Re: Keyword arguments (Was: File.open weirdness)


--Y7xTucakfITjPcLV
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Feb 16, 2002 at 12:33:23AM +0900, Paul Brannan wrote:
> The problem with the latter proposal is that it would either be
> ambiguous or make whitespace more significant than it already is, since:
>=20
>   func(arg1 :xx, arg2 :yy)
>=20
> is the same as:
>=20
>   func(arg1(:xx), arg2(:yy))
>=20
> Additionally, how would we handle:
>=20
>   func(arg1 : xx, arg2 : yy)
>=20
> since it is half-way in between?

I think you just successfully described something that guys @ apache.org ca=
ll
FS (Flexibility Syndrom), you allow parens to be left out for simple method
calls, e.g.

   print "hello"

and later on you realize that they can cause some troubles, so what's the w=
ay
out ??? define strict syntax, e.g.

method (argument: value) -> method (:argument =3D> value)
        ^^^^^^^^^
                no whitespace here allowed to indicate argument is a symbol
representing an argument of a method and not a method call taking an arg, e=
.g.

method (argument :value) -> method (argument (:value))
                 ^^^^^^
                    no whitespace here, we have a symbol

something in between should probably not be allowed at all :-?

>=20
> Paul
>=20

rgds,
martin
--=20
1024D/6E060223    2CC0 4AF6 92DA 5CBF 5F09  7BCB 6202 7024 6E06 0223
http://mman.dyndns.org/mman.gpg

--Y7xTucakfITjPcLV
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8bkkIYgJwJG4GAiMRAg1mAKCBhpvnoNNYCsWaa+/i9PAivLL9fgCcCXOA
+zw3gHANFI5lCKYwVuHVJd8=
=R1cB
-----END PGP SIGNATURE-----

--Y7xTucakfITjPcLV--