Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: murthy@margaux
To: caml-list@margaux
Subject: Convention on exceptions for caml-light
Date: Tue, 05 Jan 93 16:16:55 N	[thread overview]
Message-ID: <908.726247015@margaux.inria.fr> (raw)


What sort of schools of thought are there on the way that exceptions
should be chosen when one is writing libraries of code?

I am in the process of writing a library of modules for arrays,
strings, and lists, which will provide a common interface for all
three - so that the naming and calling conventions will be identical.
I want to also make the exception behaviour either identical or
symmetrical.  I'm not sure which.

I.e. should I declare different exceptions in each module, or should
all the modules share the same exceptions.

NJ SML seems to take the first aproach a bit, but it mixes the two a
bit.  I'm not really sure what I want, but the approach of

    Failure of string

is really easy to use, in practice.  Though, if there were a complex
piece of code, I can see that it could be hard to figure out WHERE the
error came from.





                 reply	other threads:[~1993-01-07  9:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=908.726247015@margaux.inria.fr \
    --to=murthy@margaux \
    --cc=caml-list@margaux \
    /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