public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Hughes <ahughes@redhat.com>
To: Mike Hearn <mike@plan99.net>
Cc: java@gcc.gnu.org
Subject: Re: Which library implementation to use/work on?
Date: Wed, 14 Mar 2012 12:31:00 -0000	[thread overview]
Message-ID: <89b62eb0-5a46-48e3-9dfe-6c59fe0bba07@zmail17.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <CANEZrP3_xJ9kh71=nn3GwNmYiwZ70Db+Vc+h3DKGPo_c0b9ebA@mail.gmail.com>

----- Original Message -----
> > Can you provide details please?
> 
> It's missing the usePattern method.

Ok.  This still seems to be missing in GNU Classpath (quoteReplacement was
added recently) but it looks trivial to implement.  I'll have a look myself
later today.

> 
> > How is this dead?
> 
> My mistake. I was looking at the website which does not appear to
> have
> been updated (or talk about new releases) since 2009:
> 
> http://www.gnu.org/software/classpath/
> 
> It's the one that's linked from the GCJ page.
> 

Yes, that's because the page only lists releases and there hasn't been one in
a while.  We are on the verge of 0.99; the work is done, but we're currently
stalled on GNU project admin issues in uploading the tarball :-(  I'm working
on merging 0.99 into gcj right now.

It's always a good idea to check the mailing lists of a project before posting.

> > It would help if you did a little research before making such
> > claims.
> 
> Well, that's what I'm doing right now :-)
> 

Ah good!  It just comes across a little offensive to call a project dead when
people are actively working on it :-)

> What I'm really after is CNI. I'll check out the latest classpath and
> take a look at how hard it'd be to implement the missing methods.

For CNI, you will need gcj.  Keep an eye on java-patches@gcc.gnu.org for the latest
Classpath code being merged in.

> 

-- 
Andrew :)

Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

PGP Key: 248BDC07 (https://keys.indymedia.org/)
Fingerprint = EC5A 1F5E C0AD 1D15 8F1F  8F91 3B96 A578 248B DC07

  reply	other threads:[~2012-03-14 12:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 16:57 Mike Hearn
2012-03-13 17:07 ` Andrew Haley
2012-03-13 18:26 ` Mike Hearn
2012-03-13 18:39   ` Andrew Haley
2012-03-14 10:40   ` Mike Hearn
2012-03-14 10:43     ` Chris Burdess
2012-03-14 11:11       ` Mike Hearn
2012-03-14 11:12         ` Andrew Haley
2012-03-14 12:14 ` Andrew Hughes
2012-03-14 12:17   ` Mike Hearn
2012-03-14 12:31     ` Andrew Hughes [this message]
2012-03-14 12:35       ` Mike Hearn
2012-03-14 18:32         ` Andrew Hughes
2012-03-15 12:24           ` Mike Hearn
2012-03-15 12:37             ` Andrew Hughes
2012-04-07 15:29               ` Mike Hearn
2012-04-07 18:28                 ` Bryce McKinlay
2012-04-08 13:18                   ` Mike Hearn
2012-04-10 15:53                     ` Mike Hearn
     [not found]                       ` <CANEZrP2ukT8zjNjma9yBREJ6wEuhdU6Qb=bPSOjemTYjzwrH5g@mail.gmail.com>
     [not found]                         ` <CANEZrP0QcpHjxKHWoi=A8+CcE2gPzm2_eO4_PG5=BmMHj-f_+Q@mail.gmail.com>
2012-05-30 21:14                           ` Mike Hearn

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=89b62eb0-5a46-48e3-9dfe-6c59fe0bba07@zmail17.collab.prod.int.phx2.redhat.com \
    --to=ahughes@redhat.com \
    --cc=java@gcc.gnu.org \
    --cc=mike@plan99.net \
    /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).