From: Alessandro Baretta <alex@baretta.com>
To: Brian Hurt <brian.hurt@qlogic.com>, Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Resource acquisition is initialization
Date: Thu, 12 Dec 2002 08:56:12 +0100 [thread overview]
Message-ID: <3DF8411C.90301@baretta.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0212111337130.2036-100000@eagle.ancor.com>
Brian Hurt wrote:
> On Wed, 11 Dec 2002, Blair Zajac wrote:
> The only thing I can think of which cannot tolerate the cleanup slop is
> releasing a mutex. Deleting the mutex itself is a good application for
> GC, unlocking the mutex is not.
It is not the GC which unlocks the mutex but the application
code. See Mutex.unlock .
> And for that, I think representing
> holding the lock as the lifetime of an object to be a bad idea. Were Caml
> interested more in doing multithreaded code, I'd recommend something like
> Java's synchronize keyword.
What's the difference with respect to locking a Mutex?
Alex
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-12-12 7:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 19:19 Blair Zajac
2002-12-11 19:55 ` Brian Hurt
2002-12-12 0:27 ` Chet Murthy
2002-12-12 7:56 ` Alessandro Baretta [this message]
2002-12-12 16:39 ` Brian Hurt
2002-12-13 9:22 ` Mike Potanin
2002-12-13 17:05 ` David Brown
2002-12-12 13:15 ` Xavier Leroy
2002-12-12 14:05 ` Dmitry Bely
2002-12-12 14:16 ` Xavier Leroy
2002-12-12 22:17 ` Quetzalcoatl Bradley
2002-12-12 23:59 ` Blair Zajac
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=3DF8411C.90301@baretta.com \
--to=alex@baretta.com \
--cc=brian.hurt@qlogic.com \
--cc=caml-list@inria.fr \
/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 NNTP newsgroup(s).