From: Mark Wielaard <mark@klomp.org>
To: Andrew Haley <aph@redhat.com>
Cc: Andrew John Hughes <gnu_andrew@member.fsf.org>,
Chris Gray <chris.gray@kiffer.be>,
bmckinlay <bmckinlay@gmail.com>, svferro <svferro@gmail.com>,
java <java@gcc.gnu.org>
Subject: Re: GCJ with OpenJDK Java API instead of GNU Classpath
Date: Thu, 07 May 2009 17:10:00 -0000 [thread overview]
Message-ID: <1241716199.3769.16.camel@fedora.wildebeest.org> (raw)
In-Reply-To: <4A030CE7.6050309@redhat.com>
Hi Andrew,
On Thu, 2009-05-07 at 17:31 +0100, Andrew Haley wrote:
> Mark Wielaard wrote:
> > On Thu, 2009-05-07 at 16:28 +0100, Andrew John Hughes wrote:
> >> 2009/5/7 Chris Gray <chris.gray@kiffer.be>:
> >>> Quoth Andrew John Hughes:
> >>>>> Huh? I was assuming Java compatibility was the goal.
> >>> Compatibility with the non-existent specification for Java 7, or with the
> >>> equally non-existent JCK for Java 7 (for which there is no JSR)? <G, D & R>
> >>>
> >> Neither; the JCK for OpenJDK6 which the builds of IcedTea in Fedora have passed:
> >> http://openjdk.java.net/groups/conformance/
> >
> > I don't think that is a serious option, that is only available under NDA
> > and only granted to people who sign an SCA with Sun and even then access
> > is only granted if Sun feels like it.
>
> So why is it not a serious option?
Because it isn't a thing that a free software community can do
collaboratively in the open and involves requiring proprietary software.
Maybe a third party could do it for their own binary builds, but I don't
see how we as a community can recommend it, nor would I want to
recommend it myself.
> > That said, adopting something like jigsaw for the core class library and
> > then having the option to switch modules seems a fine idea.
> > Compatibility is much more about running actually code than some opaque
> > proprietary test suite.
>
> It's about *both*. All the JCK does is make sure you've implemented the
> APIs as specified.
:) Since the JCK is under NDA that claim is not verifiable. But you
could say that the JCK assumes one particular interpretation yeah.
Still, if a secret test suite would say things should work one way, but
actual programs expect things differently I would go with not breaking
existing stuff.
Cheers,
Mark
next prev parent reply other threads:[~2009-05-07 17:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 14:31 Chris Gray
2009-05-07 15:29 ` Andrew John Hughes
2009-05-07 16:25 ` Mark Wielaard
2009-05-07 16:32 ` Andrew Haley
2009-05-07 17:10 ` Mark Wielaard [this message]
2009-05-07 17:20 ` Andrew Haley
2009-05-07 17:24 ` David Boreham
2009-05-07 17:34 ` Andrew Haley
2009-05-07 17:44 ` Mark Wielaard
2009-05-08 0:22 ` Andrew John Hughes
2009-05-08 10:13 ` Andrew Haley
2009-05-08 11:00 ` Mark Wielaard
-- strict thread matches above, loose matches on Subject: below --
2009-05-06 20:43 Sal
2009-05-07 9:17 ` Andrew Haley
2009-05-07 11:45 ` Bryce McKinlay
2009-05-07 13:25 ` Andrew John Hughes
2009-05-07 13:43 ` Andrew Haley
2009-05-07 13:50 ` Bryce McKinlay
2009-05-07 20:24 ` Sal
2009-05-08 8:04 ` Robert Schuster
2009-05-08 10:08 ` Andrew Haley
2009-05-07 16:28 ` Mark Wielaard
2009-05-08 13:47 ` Robert Schuster
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=1241716199.3769.16.camel@fedora.wildebeest.org \
--to=mark@klomp.org \
--cc=aph@redhat.com \
--cc=bmckinlay@gmail.com \
--cc=chris.gray@kiffer.be \
--cc=gnu_andrew@member.fsf.org \
--cc=java@gcc.gnu.org \
--cc=svferro@gmail.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).