From: David Allsopp <dra-news@metastack.com>
To: Ivan <ivg@ieee.org>, "caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] Lexing.position. Where to initialize field pos_fname
Date: Fri, 20 Jul 2012 07:46:54 +0000 [thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D9C2AD728A@Remus.metastack.local> (raw)
In-Reply-To: <1082921342762786@web16h.yandex.ru>
Ivan wrote:
> I'm completely lost! Can somebody teach me, where to initialize this
> field?
Documentation is in module Lexing: "See the documentation of type lexbuf for information about how the lexing engine will manage positions." and there it says that the lexing engine will update pos_cnum and "The other fields are left unchanged by the lexing engine. In order to keep them accurate, they must be initialised before the first use of the lexbuf".
So, immediately after creating/acquiring the lexbuf, you initialise lex_start_p.pos_fname
David
prev parent reply other threads:[~2012-07-20 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 5:39 Ivan
2012-07-20 6:45 ` Dan Bensen
2012-07-20 7:46 ` David Allsopp [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=E51C5B015DBD1348A1D85763337FB6D9C2AD728A@Remus.metastack.local \
--to=dra-news@metastack.com \
--cc=caml-list@inria.fr \
--cc=ivg@ieee.org \
/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