|Anonymous | Login | Signup for a new account||2014-07-23 07:25 CEST|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0006135||OCaml||OCaml documentation||public||2013-08-22 11:23||2013-09-12 15:59|
|Target Version||4.02.0+dev||Fixed in Version|
|Summary||0006135: Please document -ppx option|
|Description||Looking at the 4.01beta reference manual I cannot find -ppx!|
Apart from including -ppx it would be nice to have some basic information about ppx commands (howto read/write the syntax tree, the type of the syntax tree), as well as a pointer to more extensive documentation.
|Tags||No tags attached.|
My personal hunch is that before we know what will be done with extension_points branch (eg. integrating it in time for a 4.02 release), there are relatively few legitimate uses of -ppx, and adding extension_points in the mix would probably require an extensive reformulation of the documentation if it exists. (There already is some documentation for extension_points specifically in http://caml.inria.fr/cgi-bin/viewvc.cgi/ocaml/branches/extension_points/experimental/frisch/extension_points.txt?view=markup [^] ).
In particular, I think that using -ppx to overload the meaning of program fragments that already have a syntactic meaning in the existing OCaml language (as done in wmeyer's OMonad for experimentation purposes : http://danmey.org/omonad.html [^] ) is a bad practice that we should not encourage. The question is what other use cases remain without extension_points. There are definitely some ( it is used by an experimental version of Bisect http://bisect.x9c.fr/index.html [^] for example), but not as much as there could be in 4.02.
Of course more documentation is better than less, so if you or anyone feels motivated to write something (I guess the best thing to do for now is to look at the existing uses of -ppx to understand how to implement filters with it), I would be happy to have a look, provide feedback, and get something integrated in the manual if it's good.
Hmm. I spend a whole day making sure that every command line option is documented, both in the manual and in the man pages, for ocamlc, ocamlopt, and ocaml...
As for giving a detailed documentation of the AST types, I think like Gabriel that it's probably too early.
Hendrik Tews (reporter)
OK, I didn't know that the extensions have not been merged yet.
Then I would suggest to briefly document -ppx with the calling convention and the data type, eg
-ppx <command> Run <command> as external filter on the
abstract syntax tree after parsing. The filter
is expected to read/write a marshaled ast
of type XXX on stdin/stdout. This option will
only get useful when extension points have been
implemented in one of the following releases.
|2013-08-22 11:23||Hendrik Tews||New Issue|
|2013-08-22 11:36||gasche||Note Added: 0010226|
|2013-08-22 21:47||doligez||Note Added: 0010227|
|2013-08-22 21:47||doligez||Status||new => acknowledged|
|2013-08-22 21:47||doligez||Target Version||=> later|
|2013-08-23 11:43||Hendrik Tews||Note Added: 0010235|
|2013-09-12 15:59||doligez||Target Version||later => 4.02.0+dev|
|Copyright © 2000 - 2011 MantisBT Group|