public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Chris Abbey <jikes@cabbey.net>
To: Mauve News Group <mauve-discuss@sources.redhat.com>
Subject: Re: jacks updates
Date: Sun, 24 Oct 2004 03:44:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0410231734170.3695-100000@tweedle.cabbey.net> (raw)
In-Reply-To: <m3hdomr7yg.fsf@localhost.localdomain>

Yesterday, Tom Tromey wrote:
> 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.

I've been keeping a local copy of what I bet is the same patch for ages
now... so I certainly have no objection to moving up to something modern.

> 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?

I've never really been good at picking the location for where tests should
go in the hierarchy... it's often a subjective issue.

Perhaps tests/jcr/NNN/  ?

> 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
...
>   we could mark them so
> that we can continue testing compliance to 1.4 and 1.5.

Personally, I'm inclined to like this idea... it's likely something we
should make extensible, so for example a test could be marked as
"expect fail on < 1.5, expect pass on >= 1.5" or similar. I think we ended
up throwing away some tests that were expecting different behaviour in pre
1.2 than was seen on 1.2 and higher... and I'm sure there are tests that
behave differntly on 1.0 than any other version... and we adjusted them
with a bias against 1.0. (But 1.0 was a very different transition than 1.5
is... there was very little 1.0 code, everyone was clamouring for 1.1... I
expect there will be a lot of Java2 code for a while, the move to Java5
won't be as fast.)

-- 
Never make a technical decision based upon the politics of the situation.
Never make a political decision based upon technical issues.
The only place these realms meet is in the mind of the unenlightened.
			-- Geoffrey James, The Zen of Programming

  reply	other threads:[~2004-10-24  3:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22 17:15 Tom Tromey
2004-10-24  3:44 ` Chris Abbey [this message]
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=Pine.LNX.4.33.0410231734170.3695-100000@tweedle.cabbey.net \
    --to=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).