From: Andreas Rossberg <rossberg@mpi-sws.org>
To: Mike Lin <nilekim@gmail.com>
Cc: Yitzhak Mandelbaum <yitzhak@research.att.com>,
Andrej Bauer <Andrej.Bauer@andrej.com>,
caml-list@inria.fr
Subject: Re: [Caml-list] ocamllex and python-style indentation
Date: Wed, 1 Jul 2009 09:31:06 +0200 [thread overview]
Message-ID: <C9178E58-587B-47CA-A649-4019AB230FAD@mpi-sws.org> (raw)
In-Reply-To: <2a1a1a0c0906301913t1dce3eebie91c7cc94f015481@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 456 bytes --]
On Jul 1, 2009, at 04.13 h, Mike Lin wrote:
>>
>> Comments and string literals are no problem, since the lex wrapper
>> will
>> never see anything inside them as separate tokens anyway.
>
> OCaml comments can be nested, and must be nested parenthetically. :)
I know. (Haskell has nested comments, too, btw.) That does not make a
difference, though - it is all handled by lex already. In fact, my
code handled nested comments just fine.
- Andreas
[-- Attachment #2: Type: text/html, Size: 879 bytes --]
next prev parent reply other threads:[~2009-07-01 7:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 12:57 Andrej Bauer
2009-06-11 13:12 ` [Caml-list] " yoann padioleau
2009-06-11 13:21 ` Andreas Rossberg
2009-06-11 13:44 ` Martin Jambon
2009-06-12 8:20 ` Andrej Bauer
2009-06-12 12:56 ` Martin Jambon
2009-06-12 13:34 ` Martin Jambon
2009-06-12 15:43 ` Andreas Rossberg
2009-06-30 18:58 ` Yitzhak Mandelbaum
2009-06-30 20:19 ` Mike Lin
2009-06-30 22:06 ` Andreas Rossberg
2009-07-01 2:13 ` Mike Lin
2009-07-01 7:31 ` Andreas Rossberg [this message]
2009-07-01 14:02 ` Mike Lin
2009-07-01 14:17 ` Andreas Rossberg
2009-07-01 14:21 ` Andreas Rossberg
2009-07-01 14:37 ` Mike Lin
2009-07-01 15:03 ` Sylvain Le Gall
2009-07-01 15:16 ` [Caml-list] " Andreas Rossberg
2009-07-01 16:26 ` Sylvain Le Gall
2009-07-01 15:19 ` [Caml-list] " Martin Jambon
2009-07-01 15:43 ` Andreas Rossberg
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=C9178E58-587B-47CA-A649-4019AB230FAD@mpi-sws.org \
--to=rossberg@mpi-sws.org \
--cc=Andrej.Bauer@andrej.com \
--cc=caml-list@inria.fr \
--cc=nilekim@gmail.com \
--cc=yitzhak@research.att.com \
/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).