From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by sympa.inria.fr (Postfix) with ESMTPS id 965CF7ED47 for ; Fri, 20 Jul 2012 09:47:02 +0200 (CEST) Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of dra-news@metastack.com) identity=pra; client-ip=115.124.103.27; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="dra-news@metastack.com"; x-sender="dra-news@metastack.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail1-smtp-roc.national.inria.fr: domain of dra-news@metastack.com designates 115.124.103.27 as permitted sender) identity=mailfrom; client-ip=115.124.103.27; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="dra-news@metastack.com"; x-sender="dra-news@metastack.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@relay.metastack.com) identity=helo; client-ip=115.124.103.27; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="dra-news@metastack.com"; x-sender="postmaster@relay.metastack.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EADAMCVBzfGcb/2dsb2JhbABFuT6BB4IgAQEBBDpPAgEIGAoUEDIlAgQBGogEAgO/DZFMYAOVRIkphmCCXw X-IronPort-AV: E=Sophos;i="4.77,621,1336341600"; d="scan'208";a="167559593" Received: from relay.metastack.com ([115.124.103.27]) by mail1-smtp-roc.national.inria.fr with ESMTP; 20 Jul 2012 09:47:01 +0200 Received: from romulus.metastack.com ([81.102.132.77]) by relay.metastack.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 20 Jul 2012 08:47:01 +0100 Received: from remus.metastack.local (remus.metastack.com [172.16.0.1]) by romulus.metastack.com (8.14.2/8.14.2) with ESMTP id q6K7kuuA031902 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 20 Jul 2012 08:46:56 +0100 Received: from Remus.metastack.local ([fe80::547c:3c42:e1da:eda2]) by Remus.metastack.local ([fe80::547c:3c42:e1da:eda2%10]) with mapi id 14.02.0298.004; Fri, 20 Jul 2012 08:46:55 +0100 From: David Allsopp To: Ivan , "caml-list@inria.fr" Thread-Topic: [Caml-list] Lexing.position. Where to initialize field pos_fname Thread-Index: AQHNZjohbQHfFlf07UuXtyhJE/3tIpcxxK/A Date: Fri, 20 Jul 2012 07:46:54 +0000 Message-ID: References: <1082921342762786@web16h.yandex.ru> In-Reply-To: <1082921342762786@web16h.yandex.ru> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [212.183.128.155] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Organization: MetaStack Solutions Ltd. X-Scanned-By: MIMEDefang 2.65 on 172.16.0.20 X-OriginalArrivalTime: 20 Jul 2012 07:47:01.0997 (UTC) FILETIME=[D96CA9D0:01CD664B] Subject: RE: [Caml-list] Lexing.position. Where to initialize field pos_fname 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 fo= r 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, th= ey must be initialised before the first use of the lexbuf". So, immediately after creating/acquiring the lexbuf, you initialise lex_sta= rt_p.pos_fname David