From: Matej Kosik <5764c029b688c1c0d24a2e97cd764f@gmail.com>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: [Caml-list] Can otags process *.m{,i} files that contain macros?
Date: Sat, 11 Jan 2014 15:01:06 +0000 [thread overview]
Message-ID: <52D15CB2.8000405@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
Dear all,
I would like to ask if and how it is possible to use "otags" with files that contain macros.
E.g. if I use "mikmatch" and compile my file like this:
ocamlfind c -c -syntax camlp4o -package mikmatch_pcre main.ml
ocamlfind c -o main -syntax camlp4o -package mikmatch_pcre -linkpkg main.cmo
what is then the right way to run "otags"?
When I try:
otags -vi main.ml
I get:
File "main.ml", line 19, characters 15-16
Camlp4 parse error: [expr] expected after [infix operator (level 3) (start with '*', '/', '%')] (in [expr])
There is an "-pa" parameter, but I am not sure if I should use it and how;
(i.e., what "parser name" corresponds to "mikmatch_pcre" package.)
[-- Attachment #2: main.ml --]
[-- Type: text/plain, Size: 19 bytes --]
RE spaces = ' '*;;
reply other threads:[~2014-01-11 15:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52D15CB2.8000405@gmail.com \
--to=5764c029b688c1c0d24a2e97cd764f@gmail.com \
--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).