caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Simon Cruanes <simon.cruanes.2007@m4x.org>
To: "Raphaël Proust" <raphlalou@gmail.com>,
	"Jonathan Protzenko" <jonathan.protzenko@gmail.com>
Cc: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Literate (sort-of) programming in OCaml
Date: Mon, 02 Sep 2013 18:50:25 +0200	[thread overview]
Message-ID: <0fb7c9b0-f46a-40c1-b7b2-d7fd2be75a73@email.android.com> (raw)
In-Reply-To: <CAAmHUA=2KfZWJQx4VZidewPvuTNNe0P9dGQj74dGKrLQxDYHBQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2838 bytes --]

You may also try https://www.lri.fr/~filliatr/ocamlweb/ .

Cheers


"Raphaël Proust" <raphlalou@gmail.com> a écrit :
>On Mon, Sep 2, 2013 at 5:39 PM, Jonathan Protzenko
><jonathan.protzenko@gmail.com> wrote:
>> I am currently writing a big, mostly textual document in format blah
>> (blah being of a course a meta-variable). Are there any tools that
>> would allow me to interleave OCaml code with the contents of my
>> document?
>>
>> More on my use-case. Creating this document requires me to perform
>> various subtasks, such as:
>> - write a code snippet in the document,
>> - put the code snippet in a file,
>> - call an external program on the file,
>> - paste the output into the document.
>
>Current workflow I use involves:
>- mkfile: a rule file for mk (Plan9's take on make, it has simple
>escaping and a readable man page) to drive the whole thing,
>- bar: a compiler for the language bar that includes a Latex pretty
>printing mode
>- inc/: a directory where I place all my code samples from language bar
>- main.pdc: a pandoc file holding the source.
>
>Extracts from the mkfile:
>~~~~~~~
>TARGET=main.pdf
>SOURCE=${TARGET:%.pdf=%.pdc}
>
>INCLUDES=`{cat $SOURCE | grep '\\input{.*\.tex}' | sed
>'s/^.*\\input{([^\$\\}]*\.tex)}.*$/\1/'}
>
>$TARGET: $SOURCE $INCLUDES
>        pandoc -o $TARGET $SOURCE
>
>%.pp.tex: %.bar bar.byte
>       OCAMLRUNPARAM=$OCAMLRUNOPT ./bar.byte -latex $stem.bar > $target
>
>%.pp.annot.tex: %.bar bar.byte
>OCAMLRUNPARAM=$OCAMLRUNOPT ./bar.byte -latex -annot $stem.bar > $target
>~~~~~~~
>
>Extracts from bar.mli:
>~~~~~~~
>module type PRINTER = sig
>  val t: annotations:bool -> t -> string
>end
>module LatexPP : PRINTER
>~~~~~~~
>
>Extracts from the main.pdc
>~~~~~~~
>The annotation process, blahblah. Thus the program
>$\input{inc/foo.pp.tex}$
>is annotated in the following way: $\input{inc/foo.pp.annot.tex}$
>~~~~~~~
>
>
>Known bugs and shortcomings:
>- sed works line-wise so the mkfile INCLUDES variable is not set
>properly when there are several \input on the same line.
>- the passing of argument (using two rules with and two file
>extensions) is hackish and would not scale.
>
>
>Less painful than copy-pasting things and easier to keep everything in
>sync. It's also nice to be able to do things such as:
>\begin{align*}
><some math>\input{inc/function-application.pp.tex}<more math>\\
><more math>\input{inc/function-declaration.pp.tex}<more math>\\
><more math>\input{inc/if-then-else.pp.tex}<more math>\\
><etc.>
>\end{align*}
>
>-- 
>______________
>Raphaël Proust
>
>-- 
>Caml-list mailing list.  Subscription management and archives:
>https://sympa.inria.fr/sympa/arc/caml-list
>Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>Bug reports: http://caml.inria.fr/bin/caml-bugs

-- 
Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté.

[-- Attachment #2: Type: text/html, Size: 3330 bytes --]

  reply	other threads:[~2013-09-02 16:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-02 15:39 Jonathan Protzenko
2013-09-02 15:55 ` Alain Frisch
2013-09-02 15:59 ` Török Edwin
2013-09-02 17:26   ` Maxence Guesdon
2013-09-02 16:03 ` Roberto Di Cosmo
2013-09-02 16:29 ` Ashish Agarwal
2013-09-02 20:16   ` Jonathan Protzenko
2013-09-03  8:34     ` Alain Frisch
2013-09-03 14:34     ` Philippe Wang
2013-09-02 16:39 ` Raphaël Proust
2013-09-02 16:50   ` Simon Cruanes [this message]
2013-09-03  0:15 ` oliver
2013-09-03  9:17 ` Alan Schmitt

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=0fb7c9b0-f46a-40c1-b7b2-d7fd2be75a73@email.android.com \
    --to=simon.cruanes.2007@m4x.org \
    --cc=caml-list@inria.fr \
    --cc=jonathan.protzenko@gmail.com \
    --cc=raphlalou@gmail.com \
    /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).