From: Leo Rozenberg <leonidr@gmail.com>
To: caml-list@inria.fr
Subject: [Caml-list] executible difference between camlp4o and camlp4o.opt
Date: Wed, 14 Jul 2004 13:44:07 -0400 [thread overview]
Message-ID: <e5d671d004071410444b303b2b@mail.gmail.com> (raw)
We noticed another inconsistency between the 3.08.0 and 3.07
distributions. The 3.08.0 version was built from a modified (changed
3.07 to 3.08.0) SPEC file used to build previous RPM's.
In the 3.08.0 distribution there is inconsistent behavior between the
native and bytecode executables:
# camlp4o -v
Camlp4 version 3.08.0
# camlp4o -help
Usage: camlp4 [load-options] [--] [other-options]Load options: -I
directory Add directory in search patch for object files. -where
Print camlp4 library directory and exit. -nolib No
automatic search for object files in library directory. <object-file>
Load this file in Camlp4 core.Other options: <file> Parse this
file.
-intf <file> Parse <file> as an interface, whatever its extension.
-impl <file> Parse <file> as an implementation, whatever its extension.
-unsafe Generate unsafe accesses to array and strings.
-noassert Obsolete, do not use this option.
-verbose More verbose in parsing errors.
-loc <name> Name of the location variable (default: loc)
-QD <file> Dump quotation expander result in case of syntax error.
-o <file> Output on <file> instead of standard output.
-v Print Camlp4 version and exit.
-version Print Camlp4 version number and exit.
-help Display this list of options.
Options added by loaded object files:
-no_quot Don't parse quotations, allowing to use, e.g. "<:>" as token
# camlp4o.opt -v
# camlp4o.opt -help
leonid
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
reply other threads:[~2004-07-14 17:44 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=e5d671d004071410444b303b2b@mail.gmail.com \
--to=leonidr@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