On 8/13/06, Toby Butzon [EMAIL PROTECTED] wrote:
...
I think this is an *excellent* idea. I really like that URL-approach,
very slick. Creating a cross reference is of course a major piece
of work, but might be doable by combining ideas from eggdoc, the
man egg, svnwiki and the stuff the
Is there any existing document with sufficient metadata as to give
me a way to machine-generate the index of all of Chicken's
functions? If not, I expect I will spend a little time manually
generating this sort of data; it may be beneficial to embed it in
the existing manual (sexprs in HTML
Hello Toby,
On Sat, 12 Aug 2006 20:52:05 -0400 Toby Butzon [EMAIL PROTECTED] wrote:
On Sat, Aug 12, 2006 at 08:59:19PM -0700, Brandon J. Van Every wrote:
Typing a word into a URL is not really the kind of documentation I
want. I want to click on a word in the editor I'm using and be taken
Toby Butzon wrote:
Did you have plans for where the data for each function would come from
for your application? And are you planning to provide just the argument
list or also a description of the function? I would be happy to combine
efforts on this indexing/retrieval problem if our needs
Hi all,
My own tendancy when working with Chicken is to have a web browser
open with the R5RS index, the Chicken manual, relevant eggs, et cetera,
in separate tabs (in firefox), so lookups in the various documents are
(somewhat) convenient.
I've got some plans for a simplification of the above
Hi Brandon,
Thanks for the feedback.
On Sat, Aug 12, 2006 at 08:59:19PM -0700, Brandon J. Van Every wrote:
Typing a word into a URL is not really the kind of documentation I
want. I want to click on a word in the editor I'm using and be taken to
relevant documentation. I don't want to use
That's what eggdoc-texinfo does; when it encounters a signature it
pulls out the first element of the list, or returns the whole value if
not a list. It also returns the whole value if evaluation of the
signature fails; for example, it's pretty common to accidentally leave
off a paren at the end
