From: cashin@cs.uga.edu
To: caml-list@inria.fr
Subject: Re: [Caml-list] Re: New Features (Common Database Interface)
Date: Sat, 15 Feb 2003 08:56:55 -0500 [thread overview]
Message-ID: <874r75bqag.fsf@cs.uga.edu> (raw)
In-Reply-To: <1045262163.652.6.camel@valery5> (Matt Boyd's message of "14 Feb 2003 16:35:58 -0600")
Thanks to Matt for sharing the code, by the way.
Matt Boyd <mattwb@alve.com> writes:
...
> exception End_of_rows
> (** Raised when query results ends. *)
I didn't really read the code, but I noticed the End_of_rows exception
and I'd like to know folks' opinions about it.
I know that's analogous to End_of_file, but since an infinite number
of rows would be a lot more exceptional than a finite number, isn't
this a strange use of exceptions? I would guess that iteration or
recursion would be more efficient and expressive.
--
--Ed L Cashin | PGP public key:
ecashin@uga.edu | http://noserose.net/e/pgp/
-------------------
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
prev parent reply other threads:[~2003-02-15 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 22:35 Matt Boyd
2003-02-15 13:56 ` cashin [this message]
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=874r75bqag.fsf@cs.uga.edu \
--to=cashin@cs.uga.edu \
--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