From: Jon Harrop <postmaster@jdh30.plus.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] assertions or exceptions?
Date: Thu, 15 Jul 2004 13:35:22 +0100 [thread overview]
Message-ID: <200407151335.23097.postmaster@jdh30.plus.com> (raw)
In-Reply-To: <7f8e92aa04071501035091cbe9@mail.gmail.com>
> There are other libraries, notably Java API and .NET class library,
> that use exceptions liberaly...
OCaml and the programming styles when used in OCaml are quite different to
those of Java and most .NET languages (F# being a notable exception ;-). In
OCaml, you often write in a functional style, when performing many similar
operations this naturally lends itself to recursive functions. When running,
a deeply recursed function may suddenly find a shortcut to the correct
answer. Exceptions provide an ideal means to escape such deep recursions. The
alternative, e.g. using polymorphic options, are typically considerably less
efficient, either in terms of speed of execution or in terms of extra source
code.
This is particularly true in the context of polymorphic higher-order
functions, as the following example (hopefully!) shows.
> But why is a boolean better than an exception? Because it makes code
> simpler.
Convert the following code (which finds the product of a bunch of integers)
into an equivalent which avoids exceptions but retains the efficiency of
being able to bail earlier, upon encountering a zero:
exception Zero
let prod fold l =
try fold (fun a e -> if e=0 then raise Zero else a*e) 1 l
with Zero -> 0
> Exceptions can be left uncaught and this is a potential cause
> for a combinatorial explosion of the number of possible "execution
> paths"...
I would say it was poor style to allow the possible number of execution paths
to explode.
> 1. Is my impression that OCaml standard library is abusing exceptions
> correct?
No, it is based upon valid arguments for imperative languages which are not
applicable here.
> 2. Is it safe to assume that exceptions complicate functional
> programs as much as they complicate imperative ones?
As the above example shows, exceptions can be used to simplify code.
> 3. Is it possible to avoid using exceptions and read a text file
> line-by-line until EOF?
Yes (see other people's posts).
> 4. When do you use assertions and when do you use exceptions?
I use assertions to perform sanity checks. I use exceptions in two separate
sitations: firstly to handle exceptional circumstances, secondly to provide
an escape route from computations.
Cheers,
Jon.
-------------------
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 12:37 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
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 [this message]
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=200407151335.23097.postmaster@jdh30.plus.com \
--to=postmaster@jdh30.plus.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