From: "chris.danx" <chris.danx@ntlworld.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Records: syntax error...
Date: Tue, 18 Nov 2003 14:36:28 +0000 [thread overview]
Message-ID: <3FBA2E6C.6060701@ntlworld.com> (raw)
In-Reply-To: <3FB96A91.8000108@cs.caltech.edu>
Aleksey Nogin wrote:
> Hint: you do not have to mention the fiends that you are not interested in.
> Hint: if you want to create a new record that only slightly differs from
> an existing one, use the "with" construction:
> Hint: it is IMHO a bad style to use "match" expressions simply to check
> on a boolean value - it's much more intuitive to use "if/then/else" for
> that.
Thankyou! This is very helpful.
-------------------
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-11-18 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-18 0:23 chris.danx
2003-11-18 0:40 ` Aleksey Nogin
2003-11-18 14:36 ` chris.danx [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=3FBA2E6C.6060701@ntlworld.com \
--to=chris.danx@ntlworld.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;
as well as URLs for NNTP newsgroup(s).