public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: "java@gcc.gnu.org" <java@gcc.gnu.org>
Subject: Re: About gcj present and future
Date: Tue, 08 Jan 2013 18:06:00 -0000	[thread overview]
Message-ID: <50EC600A.6060808@redhat.com> (raw)
In-Reply-To: <CAOOf6hyQR4yLqR=89__cVr12U6tYzQW0POR0cwy=EUFX=fjk3g@mail.gmail.com>

On 01/08/2013 05:44 PM, Ernesto wrote:
>> Well, yes.  Good question.  I'd love to restart active development of
>> GCJ, but OpenJDK is free software and is way ahead in terms of
>> features.  GCJ has some advantages, but so far these haven't been enough
>> to persuade people to work on it.  If we don't do something soon it
>> may be too late.
> 
> Could you please elaborate more on "way ahead in terms of features"?
> Which features, for example?

The Classpath library is somewhere between 1.5 and 1.6.

> Must we rely on the Java Class Libraries? Providing a nice set of
> classes (an alternative framework) would be a feasible way to turn gcj
> into a new life? (another UI framework, implementations on top of
> existing native libre/open source, etc) As I told you in my first
> email, I am new on gcj so maybe the things I'm writing on are unreal,
> unfeasible or completely not applicable.

Well, it's a huge job.  A better idea IMO would be to fix gcj to use
the OpenJDK class library, which would take maybe half a programmer-
year for someone with the right experience.

Andrew.


  parent reply	other threads:[~2013-01-08 18:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08  5:26 Ernesto
2013-01-08  9:53 ` Andrew Haley
2013-01-08 17:46   ` Ernesto
     [not found]   ` <CAOOf6hyQR4yLqR=89__cVr12U6tYzQW0POR0cwy=EUFX=fjk3g@mail.gmail.com>
2013-01-08 18:06     ` Andrew Haley [this message]
2013-01-17 19:17 bbaker
2013-01-17 19:29 ` Andrew Haley

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=50EC600A.6060808@redhat.com \
    --to=aph@redhat.com \
    --cc=java@gcc.gnu.org \
    /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).