public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Adam Megacz <gcj@lists.megacz.com>
To: java@gcc.gnu.org
Subject: apologies, 3.1, mingw wishlist
Date: Tue, 09 Apr 2002 15:29:00 -0000	[thread overview]
Message-ID: <86hemkpl97.fsf@megacz.com> (raw)


First off, sorry I've been neglecting gcj recently. I needed some time
off from coding.

Second: is 3.1 still scheduled for release on 15-Apr, or has it been
pushed back?

Finally, I'm going to have a block of time Thursday through Sunday for
more Win32 work. Right now my goals are definately:

    - Fix the badly-broken notifyAll()
    - Make Win32Process work
    - Hash Synchronization (this already works, I just have to merge patches)
    - Closer review of java.io.* for proper error handling

And, if I have time:

    - Stack traces
    - Get the testsuite to run (somehow -- not sure yet how I'll do it)

Is there anything else that I should consider? After this weekend, it
might be a while before I have time to visit this again, so if there's
something you want to see, please let me know now... =)

  - a

-- 
The web is dead; long live the Internet.
http://www.xwt.org/

             reply	other threads:[~2002-04-09 22:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-09 15:29 Adam Megacz [this message]
2002-04-09 15:36 ` Tom Tromey
2002-04-09 17:50   ` Brian Jones
2002-04-11 10:57 ` Adam King
2002-04-11 12:52   ` apologies, 3.1, mingw wishlist [okay to add new ctor to ConcreteProcess?] Adam Megacz
2002-04-11 15:20     ` Tom Tromey
2002-04-11 15:53       ` Java debugger Adam King
2002-04-11 17:28         ` Nic Ferrier
2002-04-11 17:36         ` Bryce McKinlay
2002-04-11 23:13       ` apologies, 3.1, mingw wishlist [okay to add new ctor to ConcreteProcess?] Adam Megacz

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=86hemkpl97.fsf@megacz.com \
    --to=gcj@lists.megacz.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).