From: Richard Jones <rich@annexia.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] assertions or exceptions?
Date: Thu, 15 Jul 2004 14:33:59 +0100 [thread overview]
Message-ID: <20040715133359.GA13273@redhat.com> (raw)
In-Reply-To: <7f8e92aa04071505495315454@mail.gmail.com>
On Thu, Jul 15, 2004 at 03:49:19PM +0300, Radu Grigore wrote:
> Note that in your example there is always a third choice (the one
> advocated by .NET class library design guidelines): do what you do but
> also provide a function
>
> Request.valid_hostname : Request.t -> bool
I feel I might be responding to a troll here. It seems to me to be a
little obvious that you haven't done much programming OCaml, or else
you wouldn't be asking this question. There's an ocaml-beginners list
if you'd like to find out more about developing with OCaml.
Nevertheless ...
let valid_hostname r =
try ignore (Request.hostname r); true with Not_found -> false
Or, if Request.hostname had been defined the other way, then:
let valid_hostname r =
match Request.hostname r with None -> false | Some _ -> true
In practice you'd never actually write the "valid_hostname" function
explicitly, because it's so trivial to inline the code when you need
it.
> Ok, so I can hide the usage of the exception. It doesn't make me feel
> much better. It feels more like redesigning the interface of the
> standard library. (but it's a good idea nonetheless).
I happen to think that the End_of_file stuff in stdlib *is* quite
clunky. However since my main usage of files is "open file; read
entire contents into list of lines; close file", or "open file; write
this list of lines; close file", and I now have my own functions which
do both those operations in a single call, it doesn't bother me much.
Rich.
--
Richard Jones. http://www.annexia.org/ http://www.j-london.com/
Merjis Ltd. http://www.merjis.com/ - improving website return on investment
MAKE+ is a sane replacement for GNU autoconf/automake. One script compiles,
RPMs, pkgs etc. Linux, BSD, Solaris. http://www.annexia.org/freeware/makeplus/
-------------------
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:[~2004-07-15 13:34 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 8:03 Radu Grigore
2004-07-15 10:18 ` Richard Jones
2004-07-15 10:28 ` Daniel Andor
2004-07-15 12:49 ` Radu Grigore
2004-07-15 13:33 ` Richard Jones [this message]
2004-07-15 13:58 ` Radu Grigore
2004-07-16 18:53 ` Aleksey Nogin
2004-07-17 2:55 ` John Prevost
2004-07-17 14:24 ` David MENTRE
2004-07-15 12:35 ` Jon Harrop
2004-07-15 13:45 ` Radu Grigore
2004-07-15 14:33 ` Jon Harrop
2004-07-15 15:05 ` Radu Grigore
2004-07-15 16:24 ` skaller
2004-07-15 15:38 ` [Caml-list] Unboxing options, was " Brian Hurt
2004-07-15 16:25 ` John Hughes
2004-07-15 17:00 ` Brian Hurt
2004-07-15 17:20 ` John Prevost
2004-07-15 19:14 ` Radu Grigore
2004-07-15 19:56 ` John Carr
2004-07-15 20:48 ` Brian Hurt
2004-07-15 20:49 ` John Carr
2004-07-15 21:15 ` John Prevost
2004-07-15 21:15 ` Karl Zilles
2004-07-15 21:26 ` Brian Hurt
2004-07-15 21:04 ` John Prevost
2004-07-15 21:17 ` skaller
2004-07-15 21:35 ` Brian Hurt
2004-07-15 21:51 ` skaller
2004-07-15 21:42 ` skaller
2004-07-16 0:35 ` Jacques GARRIGUE
2004-07-16 1:03 ` John Prevost
2004-07-16 2:00 ` Jacques GARRIGUE
2004-07-16 16:40 ` Xavier Leroy
2004-07-19 8:58 ` Damien Doligez
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=20040715133359.GA13273@redhat.com \
--to=rich@annexia.org \
--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