From: Robert Roessler <roessler@rftp.com>
To: Caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] "lnot" missing from documented keywords list
Date: Mon, 18 Jul 2005 21:10:34 -0700 [thread overview]
Message-ID: <42DC7D3A.2000304@rftp.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0507181805540.7312-100000@localhost>
Martin Jambon wrote:
> On Mon, 18 Jul 2005, Robert Roessler wrote:
>
>
>>I just noticed this when my OCaml syntax-colorer failed to render lnot
>>as a keyword... :)
>>
>>So I checked the manual section (6.1 "Lexical conventions", subsection
>>"Keywords") that served as the reference for said syntax-colorer and
>>noticed that lnot is not there.
>>
>>Since the other "bitwise" logical operators are listed as keywords, I
>>assume this is an oversight?
>
>
> I guess these were made keywords keywords so that they can become
> infix operators. lnot doesn't have this problem since it takes only
> one argument.
Thanks, Martin - that sounds plausible, and I wondered if there was
some arcane reason for the "missing" lnot... this probably also
explains why lnot does not appear in lexer.mll - I had missed this
file on my first pass through the sources. :)
Robert Roessler
roessler@rftp.com
http://www.rftp.com
parent reply other threads:[~2005-07-19 4:10 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.LNX.4.44.0507181805540.7312-100000@localhost>]
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=42DC7D3A.2000304@rftp.com \
--to=roessler@rftp.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