From: Michel Mauny <Michel.Mauny@inria.fr>
To: Aleksey Nogin <nogin@cs.caltech.edu>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml CVS: "Warning Z: unused variable loc" in camlp4-processed files.
Date: Tue, 16 Nov 2004 18:42:15 +0100 [thread overview]
Message-ID: <20041116174215.GA15913@quincy.inria.fr> (raw)
In-Reply-To: <41969785.4060801@cs.caltech.edu>
Aleksey Nogin wrote/écrivait (Sat, Nov 13, 2004 at 03:23:49PM -0800):
> all the
> camlp4-processed files, the "EXTEND" directives end up causing a large
> number of "unused variable loc" warnings.
> So I am wondering - are there any plans for addressing this for the 3.09
> release? Thank you!
Yes: the default name for the location ident will become _loc
instead of loc. (Idents prefixed with a "_" won't be flagged as unused
even if they are.)
Existing programs using the "loc" identifier and willing to
keep it in 3.09, will have do something like:
stdpp.loc_name := "loc"
And those willing to prepare their code to 3.09 can try:
stdpp.loc_name := "_loc"
(This works in 3.08.)
Best,
-- Michel
next prev parent reply other threads:[~2004-11-16 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-13 23:23 Aleksey Nogin
2004-11-16 17:42 ` Michel Mauny [this message]
2004-11-16 17:45 ` [Caml-list] " Michel Mauny
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=20041116174215.GA15913@quincy.inria.fr \
--to=michel.mauny@inria.fr \
--cc=caml-list@inria.fr \
--cc=nogin@cs.caltech.edu \
/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