From: Nicolas Pouillard <nicolas.pouillard@gmail.com>
To: Basile STARYNKEVITCH <basile@starynkevitch.net>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] lexing from a sub-string with an explicit position
Date: Fri, 17 Feb 2006 10:57:51 +0100 [thread overview]
Message-ID: <cd67f63a0602170157g7da1c64cjb0b1c023cbab66b7@mail.gmail.com> (raw)
In-Reply-To: <20060216192329.GA4467@ours.starynkevitch.net>
On 2/16/06, Basile STARYNKEVITCH <basile@starynkevitch.net> wrote:
>
> Dear All,
Hi,
[...]
> let lxbu = Lexing.from_function stread in
> lxbu.Lexing.lex_start_p <- lpos;
> lxbu.Lexing.lex_curr_p <- lpos;
> lxbu
> ;;
Setting these fields is alas not sufficent, add this assignment should
help (it works fine for me):
lxbu.Lexing.lex_abs_pos <- lpos.Lexing.pos_cnum;
Best regards,
--
Nicolas Pouillard
prev parent reply other threads:[~2006-02-17 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 19:23 Basile STARYNKEVITCH
2006-02-17 9:57 ` Nicolas Pouillard [this message]
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=cd67f63a0602170157g7da1c64cjb0b1c023cbab66b7@mail.gmail.com \
--to=nicolas.pouillard@gmail.com \
--cc=basile@starynkevitch.net \
--cc=caml-list@yquem.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;
as well as URLs for NNTP newsgroup(s).