Quick (and possibly dirty ;) guile docs

Big News!

Texinfo qdocs! Dale Smith (cool enough to cause an ice cream headache :) has translated these messy text documents into texinfo. Pick them up here (includes dvi and info versions).

New in revision 1.1:

• Some spelling fixes :)
• Added documentation for the queue (q in normal guile) module.

The qdocs are available online here.

In progress

qdocs that I'm currently working on, but for one reason or another, haven't completed yet.

• async.[ch]: pretty close to finished.
• throw.[ch]: getting there.

Requests

If you have any requests for files you'd like to see documented, send 'em along, but keep in mind:

1. I've got about a billion things I want to get done, and these fall towards the bottom of that list.
2. This is only intended to be a temporary thing... once the manual is finished, most of this will be useless (though possibly the bits about internals would still be helpful as a guile hacking guide).
3. To document a large chunk 'o code, I have to read and understand a large chunk 'o code. I'd like a breakdown of (for example) eval.c (aka the big ugly) as much as anyone else, but eval.c is not a trivial file, and figuring out exactly what's happening throughout isn't going to be a blazingly quick process.

Helping out

Well, you can't very well expect something for nothing, now can you? >:'). Basically, if you find this stuff useful, and you know a bit about a particular part of guile that isn't here (or if I screwed up a bit that is here), just jot down something about it and send it along. It doesn't have to detail the entire file (though that would be cool :), but even an explanation of how a certain bit works would speed up the process of documenting it.

When you get to the bottom you go back to the [TOP] of the slide.

What's with this lumpy crap?

Last modified Mon Apr 19,1999

Contains some annoyances for page harvesters >;^).