From: Chris Hecker <checker@d6.com>
To: caml-list@inria.fr
Subject: non-symbol infix functions
Date: Tue, 17 Oct 2000 18:33:36 -0700 [thread overview]
Message-ID: <4.3.2.7.2.20001017181959.033bed40@walt> (raw)
This simply has to be an FAQ, but I can't find a single reference to it in the FAQ or the manual (except the BNF, which is wrong, I think).
There's no way to define an arbitrarily named infix function, right? The BNF in the manual implies you can't do it. But at the same time, that BNF implies you can't have "external" infix operators that aren't value-names (which have to be either lowercase-ident or ( operator-name )). Yet, pervasives.mli has "external (lsl)..." in it.
So, why can there be an external (lsl) but not a let (lsl) x y = ...? If it's true that you can't do it internally, why did you guys bother hacking lsl and the other bit ops to be infix, since it breaks consistency (and taunts the programmer with a non-symbol infix operator the likes of which he can't make himself)?
Perhaps this should be added to the FAQ?
Chris
next reply other threads:[~2000-10-18 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-18 1:33 Chris Hecker [this message]
2000-10-18 9:29 ` Pierre Weis
2000-10-18 9:44 ` Chris Hecker
2000-10-18 13:30 ` Pierre Weis
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=4.3.2.7.2.20001017181959.033bed40@walt \
--to=checker@d6.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