From: Ranjit Mathew <rmathew@gmail.com>
To: mauve-discuss@sources.redhat.com
Subject: Re: Keeping Jacks Up-to-date
Date: Sat, 17 Sep 2005 17:04:00 -0000 [thread overview]
Message-ID: <dghi45$m58$1@sea.gmane.org> (raw)
In-Reply-To: <m3hdcjd9m7.fsf@localhost.localdomain>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tom Tromey wrote:
>>>>>>"Ranjit" == Ranjit Mathew <rmathew@gmail.com> writes:
>
>
> Ranjit> Does anyone have any objections to moving Jacks to JLS 3rd
> Ranjit> Edition?
>
> Nope.
Thanks.
> Ranjit> 3. Removing tests that are no longer wrong. For example,
> Ranjit> auto-boxing in JLS 3 invalidates some of the testcases.
>
> How about making them conditional so that people can continue to test
> 1.4 compilers? I think this is probably worthwhile for the next year
> or so.
Yes, that'll be better, though I'm not sure of the Tcl incantations
necessary to achieve that.
[I notice that there are separate constraints called "jsr201" and
"staticImport" - AFAIK, JSR201 included static import (along with
auto-boxing, enhanced for, etc.). And I also notice that mainline
GCJ's gcj_setup should switch off for these constraints.]
Ranjit.
- --
Ranjit Mathew Email: rmathew AT gmail DOT com
Bangalore, INDIA. Web: http://ranjitmathew.hostingzero.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDLEwxYb1hx2wRS48RAm7TAJ9mlXZ6+V/yOc1h7GczRh4dPSl8WgCbBBny
5Q5rM/1BS98kma1fN4GR1UA=
=vnfp
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-09-17 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 3:03 Ranjit Mathew
2005-09-17 15:03 ` Tom Tromey
2005-09-17 17:04 ` Ranjit Mathew [this message]
2005-09-19 14:49 ` Tom Tromey
2005-09-20 6:10 ` Ranjit Mathew
2005-09-20 14:43 ` Tom Tromey
2005-09-21 5:08 ` Ranjit Mathew
2005-09-22 15:47 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='dghi45$m58$1@sea.gmane.org' \
--to=rmathew@gmail.com \
--cc=mauve-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).