public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Ranjit Mathew <rmathew@gmail.com>
To: mauve-discuss@sources.redhat.com
Subject: Keeping Jacks Up-to-date
Date: Sat, 17 Sep 2005 03:03:00 -0000	[thread overview]
Message-ID: <dgg0sn$js7$1@sea.gmane.org> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

  Does anyone have any objections to moving Jacks to JLS 3rd
Edition?

This would mean:

  1. Updating jacks.html to note the same with a caveat that work is
     still in progress so some tests might be out-of-date.

  2. Updating references to various JLS sections. For example the
     current tests for "jls/definite-assignment/statements/while-
     statements" refer to section 16.2.9, whereas the new JLS has
     it in 16.2.10.

  3. Removing tests that are no longer wrong. For example,
     auto-boxing in JLS 3 invalidates some of the testcases.

  4. Writing tests for the new features, most notably, generics.
     (I see that this is already happening.)

I presume that patches to Jacks ought to be sent to mauve-patches.

Thanks,
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

iD8DBQFDK4dCYb1hx2wRS48RAv/3AJ4hVH7qVyAog1jrKM1k4fQyxCe3WQCeJEBA
AhA7Vpq6x1ASL75MjXQrCwk=
=YclN
-----END PGP SIGNATURE-----

             reply	other threads:[~2005-09-17  3:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-17  3:03 Ranjit Mathew [this message]
2005-09-17 15:03 ` Tom Tromey
2005-09-17 17:04   ` Ranjit Mathew
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='dgg0sn$js7$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).