From: Christophe Raffalli <christophe.raffalli@univ-savoie.fr>
To: caml-list <caml-list@inria.fr>
Subject: camlp4 char stream
Date: Sun, 11 Sep 2005 22:19:36 +0200 [thread overview]
Message-ID: <43249158.4070900@univ-savoie.fr> (raw)
I would like to know how I can access directly the input char stream in
camlp4
i want a
c-code { ... }
producing an empty str_item, but consuming the c-code in the { ... "}
and outputing it in a separate file. An easy way is to access directly
the char stream, but I do not find it (actually, looking at the source
it is not stored in an accessible variable.
Someonce see a solution, other that parsing a string ?
[ [ c_code STRING -> ... ] ] would be easy, but is not very satisfactory.
next reply other threads:[~2005-09-11 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 20:19 Christophe Raffalli [this message]
2005-09-11 21:51 ` [Caml-list] " Martin Jambon
2005-09-12 5:39 ` Christophe Raffalli
2005-09-12 6:40 ` Martin Jambon
2005-09-12 13:27 ` Olivier Andrieu
2005-09-12 22:31 ` Pietro Abate
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=43249158.4070900@univ-savoie.fr \
--to=christophe.raffalli@univ-savoie.fr \
--cc=caml-list@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).