public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Jeroen Frijters" <jeroen@sumatra.nl>
To: "Stephen Crawley" <crawley@dstc.edu.au>,
	"Mark Wielaard" <mark@klomp.org>
Cc: "Noa Resare" <noa@resare.com>,
	"Mauve Discuss" <mauve-discuss@sources.redhat.com>,
	<crawley@piglet.dstc.edu.au>, <crawley@piglet.dstc.edu.au>
Subject: RE: gnu/testlet/java/nio/channels/FileChannel/manyopen.java broken
Date: Mon, 11 Oct 2004 06:39:00 -0000	[thread overview]
Message-ID: <D92197D0A6547B44A1567814F851FA687DF4@LEMBU.sumatrasoftware.com> (raw)

Stephen Crawley wrote:
> Java programs that rely on the GC to find / close file handles are
> non-portable and (IMO) broken.  A portable program cannot depend on
> the GC running soon enough to get around a problem with running
> out of file descriptors.

While I agree with your general point (and that this test shouldn't be
in Mauve), I would like to add a small footnote:

The nio memory mapped file API *requires* you to rely on the GC to close
the files.

Personally, I happen to think that the API is broken because of this,
but as of 1.4 (haven't looked at 1.5 yet) this is the sad reality.

Regards,
Jeroen

             reply	other threads:[~2004-10-11  6:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-11  6:39 Jeroen Frijters [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-08  6:35 Noa Resare
2004-10-08  6:47 ` Stephen Crawley
2004-10-08 10:05   ` Mark Wielaard
2004-10-08 11:07     ` Noa Resare
2004-10-08 17:00     ` Thomas Zander
2004-10-11  0:50     ` Stephen Crawley

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=D92197D0A6547B44A1567814F851FA687DF4@LEMBU.sumatrasoftware.com \
    --to=jeroen@sumatra.nl \
    --cc=crawley@dstc.edu.au \
    --cc=crawley@piglet.dstc.edu.au \
    --cc=mark@klomp.org \
    --cc=mauve-discuss@sources.redhat.com \
    --cc=noa@resare.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).