From: Claudio Trento <trento@di.unipi.it>
To: caml-list@inria.fr
Subject: [Caml-list] Associativity precedence for the user-defined operator.
Date: Fri, 23 Jul 2004 16:27:06 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0407231614060.12107-100000@strudel.di.unipi.it> (raw)
Hi,
I've defined a set of new operetors, for instance:
let ( /+/ ) = add_num (where add_num is a function that added two sometype
elements.)
but I don't know if I can set associativity precedence for this operator,
writing: el1 ( /+/ ) el2 ( /+/ ) el3 without parenthesis, what happens?
Cheers,
Claudio
-------------------
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 reply other threads:[~2004-07-23 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 14:27 Claudio Trento [this message]
2004-07-23 14:36 ` Richard Jones
2004-07-23 17:42 ` Jean-Baptiste Rouquier
2004-07-23 19:52 ` John Prevost
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=Pine.LNX.4.44.0407231614060.12107-100000@strudel.di.unipi.it \
--to=trento@di.unipi.it \
--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).