> As far as I can tell, neither your script nor org-babel mode address the
> third prong of literate programming as defined by Knuth, specifically, the
> extensive cross-indexing, letting you know not only where functions are
> defined, but also where defined functions are used. Why do you not
> consider this to be as essential as, say, the ability to reorder your code?
I do this with a latex macro. I have a "calls" macro that reads:
\calls{thisfn}{theFunctionCalled}
which creates
thisfn 77
calls theFunctionCalled 42
theFunctionCalled 42
called by thisfn 77
in the index. I use the hyperref latex package so each of these
becomes a hyperlink into the book. I have considered writing an
emacs function to generate the lines but it takes so little work
that I can't be bothered. I cons up an emacs keystroke macro,
point at the function called, and it adds the \calls line at
the head of the function. Point, C-x e, and it's done.
The index is really useful when reading or refactoring because I
can find all of the callers of a function by just looking at the
back of the book.
I probably should add the \calls macro to the clojure pamphlet.
Tim
--
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
