From: "Jérémie Dimino" <jeremie@dimino.org>
To: "Dash, Santanu" <s.dash@herts.ac.uk>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] file specific outputting
Date: Tue, 10 Jul 2012 14:16:44 +0200 [thread overview]
Message-ID: <20120710141644.7eec1b5a@caladan.esterel-technologies.com> (raw)
In-Reply-To: <CEDE565C-6DB2-40FF-9967-8E93DEACAE5E@herts.ac.uk>
Le Tue, 10 Jul 2012 11:50:24 +0100,
"Dash, Santanu" <s.dash@herts.ac.uk> a écrit :
> Can someone direct me on the best way to go about this? Is there a
> variable in the compiler that stores the filename of the file
> currently being compiled?
There is Location.input_name. It is set by the compiler before parsing
a source file (file "driver/pparse.ml", function "file"). Note that if
there are multiple source files on the command line it will be
modified for each one of them.
--
Jérémie
next prev parent reply other threads:[~2012-07-10 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 10:50 Dash, Santanu
2012-07-10 11:21 ` Gabriel Scherer
2012-07-10 12:16 ` Jérémie Dimino [this message]
2012-07-10 12:39 ` Dash, Santanu
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=20120710141644.7eec1b5a@caladan.esterel-technologies.com \
--to=jeremie@dimino.org \
--cc=caml-list@inria.fr \
--cc=s.dash@herts.ac.uk \
/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).