From: Tom Tromey <tromey@redhat.com>
To: Michael Koch <konqueror@gmx.de>
Cc: classpath@gnu.org, mauve-discuss@sources.redhat.com
Subject: Re: Java 5 features
Date: Wed, 08 Mar 2006 17:35:00 -0000 [thread overview]
Message-ID: <m3lkvk6dzj.fsf@localhost.localdomain> (raw)
In-Reply-To: <20060307193846.GL18158@asterix.konqueror.de>
>>>>> "Michael" == Michael Koch <konqueror@gmx.de> writes:
Michael> What is the state of support for the Java 5 language features
Michael> in Mauve? Is it okay to use Generics and Enums and such
Michael> stuff in testcases that are tagged "1.5"? I would like to
Michael> commit some testcases that use Generics and Enums to test
Michael> some stuff in GNU classpath generics branch.
Michael> What's your opinion?
The problem with doing this is that it means that parts of Mauve
won't compile against classpath head. This in turn means that an
eclipse checkout will always show errors.
I suppose if we put these tests into a segregated part of the
directory tree we could easily turn them off in the eclipse build.
Perhaps we could just disable eclipse compilation of individual
files, I haven't looked...
Another idea would be to make a generics branch for mauve and then
merge it when we do the merge for classpath.
Tom
prev parent reply other threads:[~2006-03-08 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 18:34 Michael Koch
2006-03-08 17:35 ` Tom Tromey [this message]
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=m3lkvk6dzj.fsf@localhost.localdomain \
--to=tromey@redhat.com \
--cc=classpath@gnu.org \
--cc=konqueror@gmx.de \
--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).