From: David Teller <David.Teller@univ-orleans.fr>
To: Brian Hurt <bhurt@janestcapital.com>
Cc: Jon Harrop <jon@ffconsultancy.com>, caml-list@inria.fr
Subject: Re: [Caml-list] [OSR] OCaml Standard Recommandation Process
Date: Mon, 28 Jan 2008 18:30:40 +0100 [thread overview]
Message-ID: <1201541440.6747.68.camel@Blefuscu> (raw)
In-Reply-To: <479E04E6.5000303@janestcapital.com>
A few things here:
* we can provide two libraries, one with monads and one without, and let
users choose whichever they use
* it's quite easy to build a generic resource-disposal facility on par
with 'use' or 'try...finally...', even without resorting to Camlp4 -- I
leave that as an exercise to the reader or to the time when we decide to
start an OSR thread on that issue
* in any case, there's no need to change OCaml itself to do any of
these, or even to add a IDisposable interface and an object-oriented
hierarchy, only the distribution.
Let me remind you that the initial topic of the thread was to agree upon
a discussion process, not to debate on a specific issue.
So do we agree on the OSR process as I've described it or does anyone
believe we should first change it ?
Cheers,
David
On Mon, 2008-01-28 at 11:37 -0500, Brian Hurt wrote:
> Monads strike me as being a better way to do this, but again, we're talking about deep changes to Ocaml. The alternative- wait until the object is garbage collected, depends upon the form of the garbage collector.
--
David Teller
Security of Distributed Systems
http://www.univ-orleans.fr/lifo/Members/David.Teller
Angry researcher: French Universities need reforms, but the LRU act brings liquidations.
next prev parent reply other threads:[~2008-01-28 17:30 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 13:23 David Teller
2008-01-27 13:52 ` [Caml-list] " Paolo Donadeo
2008-01-27 14:24 ` Yaron Minsky
2008-01-27 19:07 ` David Teller
2008-01-27 21:07 ` Jon Harrop
2008-01-27 21:47 ` Yaron Minsky
2008-01-28 11:06 ` David Teller
2008-01-28 12:04 ` Jon Harrop
2008-01-28 12:31 ` David Teller
2008-01-28 14:23 ` Brian Hurt
2008-01-28 15:15 ` Loup Vaillant
2008-01-28 15:40 ` Brian Hurt
2008-01-28 19:46 ` Jon Harrop
2008-01-28 15:25 ` Jon Harrop
2008-01-28 16:06 ` Christophe TROESTLER
2008-01-28 16:20 ` Nicolas Pouillard
2008-01-28 16:45 ` Christophe TROESTLER
2008-01-28 16:51 ` Olivier Andrieu
2008-01-28 19:58 ` Jon Harrop
2008-01-29 7:51 ` Gordon Henriksen
2008-01-28 20:49 ` Jon Harrop
2008-01-28 22:05 ` Till Varoquaux
2008-01-28 23:10 ` Jon Harrop
2008-01-28 16:37 ` Brian Hurt
2008-01-28 17:30 ` David Teller [this message]
2008-01-28 20:43 ` Jon Harrop
2008-01-28 21:12 ` Gerd Stolpmann
2008-01-28 21:39 ` Jon Harrop
2008-01-29 16:49 ` Edgar Friendly
2008-01-30 8:52 ` Sylvain Le Gall
2008-01-30 10:02 ` [Caml-list] " Jon Harrop
2008-01-30 12:12 ` Vincent Hanquez
2008-01-28 21:43 ` [Caml-list] " Dario Teixeira
2008-01-29 7:59 ` Francois Pottier
2008-01-28 22:07 ` Arnaud Spiwack
2008-01-27 14:36 ` Michaël Grünewald
2008-01-27 15:10 ` Dario Teixeira
2008-01-28 13:38 ` Sylvain Le Gall
2008-01-28 13:52 ` [Caml-list] " David Teller
2008-01-28 0:23 ` [Caml-list] " Oliver Bandel
2008-01-30 9:43 ` Sylvain Le Gall
2008-01-30 20:25 ` [Caml-list] " blue storm
2008-01-30 20:49 ` Sylvain Le Gall
2008-01-30 20:54 ` [Caml-list] " Eric Cooper
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=1201541440.6747.68.camel@Blefuscu \
--to=david.teller@univ-orleans.fr \
--cc=bhurt@janestcapital.com \
--cc=caml-list@inria.fr \
--cc=jon@ffconsultancy.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