From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: caml-list@inria.fr
Subject: [Caml-list] a few lexing questions
Date: Mon, 28 Apr 2003 14:13:48 -0400 [thread overview]
Message-ID: <20030428181348.GM9337@alan-schm1p> (raw)
Hi,
I am writing a parser / pretty-printer for the iCalendar file format,
and I have a few questions.
First of all, there are some times when I need to differentiate lexing
according to the first letter of what I am lexing. As I want to reuse
the lexing code, I did the following:
and alt_lang_xparam = parse
| 'A' { lexbuf.Lexing.lex_curr_pos <- Lexing.lexeme_start lexbuf;
Altrepparam (altrepparam lexbuf) }
| 'X' { lexbuf.Lexing.lex_curr_pos <- Lexing.lexeme_start lexbuf;
Xparam (xparam lexbuf) }
| 'L' { lexbuf.Lexing.lex_curr_pos <- Lexing.lexeme_start lexbuf;
Langparam (languageparam lexbuf) }
Is it buggy ? Bad style ? Is there a nicer way to do it ?
A second question is about integration this code with other lexing code
or streams. An iCalendar file cannot have a line that is longer than 75
bytes, excluding line break. A line may be broken anywhere as long as
there is a space at the beginning of the next line, as in:
this is a very lo
ng line
represents "this is a very long line". As this break may occur anywhere
(even inside keywords), I assume when writing the lexer these kind of
lines have been already merged together. I know how to implement the
merging using a temp file, but I'm looking for a nicer solution (like
using a stream, or using one lexer to feed the current lexer). Any
suggestion ?
I'd also like to have some advice on doing the symmetric transformation
(breaking long lines when necessary) ... Would streams be a good
solution here ?
Thanks a lot,
Alan Schmitt
--
The hacker: someone who figured things out and made something cool happen.
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next reply other threads:[~2003-04-28 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 18:13 Alan Schmitt [this message]
2003-04-28 21:30 ` Michal Moskal
2003-04-30 12:31 ` John Max Skaller
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=20030428181348.GM9337@alan-schm1p \
--to=alan.schmitt@polytechnique.org \
--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