Wonderful!
I'll try to help with whatever I can (if I don't drive you nuts =).
A few points on the order of entries in your table of contents to be.
* Getting started
Introduction -> Introduction to pike Installation -> Installing pike
Perhaps you should consider the order of the available methods of installing to be somewhat closer to the most common case? I'm thinking
* Installing precompiled Pike binaries * Installing Pike from source * Installing Pike from CVS
Maybee the section on Using hilfe should be moved up. It is after all a rather easy and helpful first encounter with pike.
* The Pike Language
Lowercase the type names (nitpicking)
Basic Datatypes
Add the mixed type. Add zero type (? if mentioned here, perhaps only briefly).
Container datatypes
I'm curious, quite possible dumbstruck, but how is a function a object datatype? Isn't this a basic datatype?
Control statements Add for and foreach.
Operators and Expressions Perhaps a subsection on syntactic sugar? Like a[*] + b[*] (can't think of anything else ATM).
Er.. this is starting too look rather unstructured, so i'll stop here for the time beeing.
Also, If this get's busy - perhaps there would be use of a pike documentation meeting/list?
/ Peter Lundqvist (disjunkt)
Previous text:
2003-12-21 17:40: Subject: More conference items: book and mailing list
Hi All,
[apologies in advance for the cross-posting, i wasn't sure of the coverage on both lists]
I've been going through some of the items from the conference, and I thought I'd take a little initiative. To that end, here's an update:
- A pike book
I've decided to start work on Pike book. My target is somewhere between the tutorial and the source code or modref. That is, a relatively complete reference to the most important parts of the language such as constructs and important features, but not a function reference (important functions such as Stdio and the like will be covered). My plan is to assume basic programming knowledge that isn't necessarily assumed in the current tutorial online. I've gotten a good bit of feedback regarding what's missing, from programming savvy individuals that have tried to pick up pike.
I've placed a first crack at a table of contents here:
http://hww3.riverweb.com/dist/PikeManual.txt
Any and all feedback would be greatly appreciated (additions, deletions, reorganizations, etc)
Also, unrelated to this effort, I was wondering who owned the copyright on the current tutorial... does anyone know? I was thinking of getting a few copies of this material printed and bound, but don't want to end up with a lawyer at my door. If there's interest from anyone out there, please let me know.
- The pike@roxen.com mailing list archive
As part of my research into topic #1 above, I got thinking that there's a large amount of good information locked away in the mailing list archives. Unfortunately, the only way to get at it right now is to use the mailing list archive server, which is relatively inconvenient. In order to remedy this situation, I've put a very simple, searchable archive online here:
http://modules.gotpike.org:8000/list/
It's not fulltext search (my mysql is apparently not happy about doing fulltext), but it does use substring searching, so it's at least as good as a simple grep. It will probably move to a more suitable location in the future. Thanks to Martin Bahr for the archive mailbox, going back 7 years.
As always, comments and feedback are welcome...
Bill
/ Brevbäraren