From: John Whitley <whitley@cse.buffalo.edu>
To: caml-list@inria.fr
Subject: Functional composition operator?
Date: Tue, 8 Dec 1998 00:23:59 -0500 (EST) [thread overview]
Message-ID: <13932.45585.522844.651609@hadar.cs.Buffalo.EDU> (raw)
Andrew Kay <akay@sharp.co.uk> wrote, in the caml-list archives:
> We are in the process of converting our Caml code into OCaml, and
> have a problem choosing an infix syntax for function composition
> [...] What do other OCaml people use for function composition? Is
> there standard emerging?
I found no answer in the archives, so I'd like to raise the same
question again: is there a consensus for choice of infix composition
operator? Failing that, is there some design principle that warranted
its omission?
Thanks,
John Whitley
next reply other threads:[~1998-12-08 17:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-08 5:23 John Whitley [this message]
1998-12-08 17:02 ` Pierre Weis
1998-12-08 21:52 ` John Harrison
1998-12-09 10:58 ` Pierre Weis
1998-12-09 17:17 ` John Harrison
1998-12-11 13:57 ` Pierre Weis
1998-12-08 18:08 Andrew Kay
1998-12-08 20:32 ` John Prevost
1998-12-09 16:17 ` Anton Moscal
1998-12-08 19:51 Don Syme
1998-12-08 20:09 Don Syme
1998-12-09 12:00 Don Syme
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=13932.45585.522844.651609@hadar.cs.Buffalo.EDU \
--to=whitley@cse.buffalo.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