public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Mauve News Group <mauve-discuss@sources.redhat.com>
Cc: Chris Abbey <jikes@cabbey.net>
Subject: jacks updates
Date: Fri, 22 Oct 2004 17:15:00 -0000	[thread overview]
Message-ID: <m3hdomr7yg.fsf@localhost.localdomain> (raw)

Ok, I've checked in the minor Jacks bug fixes I've collected from the
recent past.  Mostly just typos, but also an additional test for
method overriding (it seems that we could use more here) and a real
fix to some test output.

I also have a patch to change jacks to use tclsh8.4 -- I made this
change locally since FC2 doesn't ship tclsh8.3.  If nobody objects
I'll make this change in the mauve cvs repository as well.

Also, I have some tests (some by me, some posted to the jacks list
this year) for 1.5 things: boxing, foreach, and enums.  In my
repository I have these in tests/non-jls/, but I suppose they probably
belong in tests/jls now.  Chris, what do you think?

Also there's the question of what to do about code that was invalid
in 1.4 but is now valid in 1.5.  For instance something like

    Object x = 5;

falls into this category due to auto-boxing.  We could either modify
these tests so that they are always invalid, or we could mark them so
that we can continue testing compliance to 1.4 and 1.5.  I'm inclined
toward the latter offhand.

Tom

             reply	other threads:[~2004-10-22 17:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22 17:15 Tom Tromey [this message]
2004-10-24  3:44 ` Chris Abbey
2004-10-25 19:35   ` 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=m3hdomr7yg.fsf@localhost.localdomain \
    --to=tromey@redhat.com \
    --cc=jikes@cabbey.net \
    --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).