This is the mail archive of the
kawa@sourceware.org
mailing list for the Kawa project.
Re: bug #27553 - patch
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> In Java, it supports two ways.
> snip...
> In R5RS of DrRacket, it supports two ways too.
I was aware of the R^n standards, as well as Java behaviour, that's what
I meant by "consistency". Furthermore, the Q2 language throws an
identical exception to the behaviour this patch implements. That's all I
was thinking when I talked of consistency.
> I don't know if the current behaviour is a good idea - but it is
> intentional.
It makes sense to have this notion, I now understand why this was being
done the way it was. It seems that if you mimic the Java or Scheme way
of dealing with this, you get the benefits you speak of, but you won't
surprise anyone.
> An idiom like (substring 0 -1), which returns all expect the last
> element, is very convenient and used in many languages.
FWIW, I think that's a bad idea.
Thanks all for the feedback.
Charles.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNpC7AAAoJEG9M6fiX7bE4660IALlwTrq3zreAXYuGv9GhWM/d
ReW5yLNe7TqXb9fYvWUG9RhDO//xZsuQnSPMwLhijlj1L+nBITKYaqStZsfiNzQa
E2NM5JbOl8IVnhrJ4FwOD+dVhRF0Mc08MMVUMOr0e9gfhT+w+ncnmKwssXCVimwy
7DMZJWIRwpwLuJa/xZbOlzjsdwwP6tIy8zee50qahSI8FWwBn/e/BfjSQJLQFVF1
N1KR9eOMHVkkbbw0cflwNNPYC3OEgCwaXIimTIoC40ZFqT1OEzwfFfJsf8BNG0Fx
vACvW1sSdnyseMtZb1Ki8oK2zMMf0DgAgp66UQ+uWmRELBA144me7IjeKd1yjOI=
=8xWH
-----END PGP SIGNATURE-----