From: Gabriel Kerneis <gabriel.kerneis@enst.fr>
To: caml-list@yquem.inria.fr
Subject: Record types "with" syntax and camlp4
Date: Wed, 21 Feb 2007 19:34:33 +0100 [thread overview]
Message-ID: <20070221193433.07f5981b@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 538 bytes --]
Hi,
the { x with y = z} syntax seems to be broken in camlp4. But i can't
find any information about it in the (deprecated ?) camlp4 manual.
19:29 gabriel % cat record.ml
type t = { a : int ; b : float } ;
value x =
let s = {a=5 ; b= 1.5} in
{s with b = 4.1} ;
19:29 gabriel % camlp4rf record.ml
File "record.ml", line 4, characters 8-12:
Parse error: [fun_binding] expected after [label_longident] (in
[label_expr])
zsh: exit 2 camlp4rf record.ml
Any hint ?
Thanks a lot,
--
Gabriel Kerneis
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-02-21 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 18:34 Gabriel Kerneis [this message]
2007-02-22 9:46 ` [Caml-list] " Nicolas Pouillard
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=20070221193433.07f5981b@localhost \
--to=gabriel.kerneis@enst.fr \
--cc=caml-list@yquem.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).