From: Andrew Haley <aph@redhat.com>
To: Ruben De Smet <ruben.de.smet@telenet.be>, java@gcc.gnu.org
Subject: Re: Java > 1.5
Date: Sat, 16 Aug 2014 08:13:00 -0000 [thread overview]
Message-ID: <53EF12B3.7000600@redhat.com> (raw)
In-Reply-To: <53EE496B.9020709@telenet.be>
On 15/08/14 18:54, Ruben De Smet wrote:
> Dear java@gcc.gnu.org list,
>
> I've gotten to compile some things with GCJ (hooray!) which don't run
> fine (ooooh). If I don't come to run it on my own, I'll certainly file a
> bug report or contact this list.
>
> I would like to avoid having to distribute a Java runtime to users, but
> my teammate is writing code in Java 1.7. I read GCJ only understands 1.5.
>
> Is there any development going on for Java 1.7? Would it be a lot of
> work to implement some Java 1.7 features? I would take it on me if needed.
Right now there's not much prospect of that. The problem is the class
libraries, which would require a lot of work. The best prospect is to
convert libgcj to use the libraries from OpenJDK, which would work,
but again the conversion would take maybe 6 months for someone who
knows gcj very well, along with some compiler changes. It could be
done, but there needs to be a compelling reason.
> There were two things I noticed with my teammates code that were using
> 1.7 features. @Override on interfaces and multi exception catch (like
> catch (IOException | OtherException e) ).
I'm sure it's possible.
Andrew.
next prev parent reply other threads:[~2014-08-16 8:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 17:54 Ruben De Smet
2014-08-16 8:13 ` Andrew Haley [this message]
2014-08-16 9:44 ` Ruben De Smet
2014-08-16 22:59 ` Andrew Haley
2014-08-17 8:55 ` Ruben De Smet
2014-08-17 16:00 ` Andrew Haley
2014-08-16 10:33 ` Brian Jones
2014-08-16 10:37 ` Ruben De Smet
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=53EF12B3.7000600@redhat.com \
--to=aph@redhat.com \
--cc=java@gcc.gnu.org \
--cc=ruben.de.smet@telenet.be \
/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).