From: Martin Jambon <martin.jambon@ens-lyon.org>
To: Sylvain Le Gall <sylvain@le-gall.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: ocamllex and python-style indentation
Date: Wed, 01 Jul 2009 17:19:27 +0200 [thread overview]
Message-ID: <4A4B7E7F.3040908@ens-lyon.org> (raw)
In-Reply-To: <slrnh4mulo.hil.sylvain@gallu.homelinux.org>
Sylvain Le Gall wrote:
> Hello,
>
> On 01-07-2009, Andreas Rossberg <rossberg@mpi-sws.org> wrote:
>> Mike Lin wrote:
>>> OK, now I'm curious :) how does your lexer match balanced parentheses,
>>> or in this case comments?
>>>
>> Easily, with a bit of side effects (I think that's roughly how all ML
>> compilers do it):
>>
>> ------------------------------------------------
>> let error l s = (* ... *)
>> let commentDepth = ref 0
>> let start = ref 0
>> let loc length = let pos = !start in (pos, pos+length)
>>
>> rule lex =
>> parse eof { EOF }
>> (* | ... *)
>> | "{-" { start := pos lexbuf;
>> lexNestComment lexbuf }
>>
>> and lexNestComment =
>> parse eof { error (loc 2) "unterminated comment" }
>> | "(*" { incr commentDepth;
>> lexNestComment lexbuf }
>> | "*)" { decr commentDepth;
>> if !commentDepth > 0
>> then lexNestComment lexbuf
>> else lex lexbuf }
>> | _ { lexNestComment lexbuf }
>> ------------------------------------------------
>>
>> If you also want to treat strings in comments specially (like OCaml),
>> then you need to do a bit more work, but it's basically the same idea.
>>
>
> May I recommend you to write this in a more simple way:
>
> -------------------------------------------------------------------------
> rule lex =
> parse eof { () }
> | "(*" { start := pos lexbuf; lexNestComment lexbuf; lex lexbuf }
>
> and lexNestComment =
> parse eof { error (loc 2) "unterminated comment" }
> | "(*" { lexNestComment lexbuf }
> | "*)" { () }
> | _ { lexNestComment lexbuf }
> -------------------------------------------------------------------------
>
> I think it works the same way, except that it uses less global
> variables.
You can even get rid of global variables completely:
rule lex x = parse
eof { () }
| "(*" { x.start <- pos lexbuf; lexNestComment x lexbuf; lex x lexbuf }
and lexNestComment x = parse
eof { error (loc x 2) "unterminated comment" }
| "(*" { lexNestComment x lexbuf }
| "*)" { () }
| _ { lexNestComment x lexbuf }
Martin
--
http://mjambon.com/
next prev parent reply other threads:[~2009-07-01 15:25 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
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 ` Martin Jambon [this message]
2009-07-01 15:43 ` [Caml-list] " 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=4A4B7E7F.3040908@ens-lyon.org \
--to=martin.jambon@ens-lyon.org \
--cc=caml-list@inria.fr \
--cc=sylvain@le-gall.net \
/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