hi,
when trying to look something up about pike syntax it occured to me that there is no syntax reference. the chapturized reference manual has some of it, but where do i eg find a complete(!) description of eg inherit. ?
just like the module reference a reference for all keywords would be nice.
besides that, the titles module tree quick reference and complete chapterized reference manual are a bit confusing.
the module tree reference isn't exactly quick but rather complete nowadays, while the features of pike have surpassed the chapterized manual making it incomplete.
i'd suggest to change the titles to:
module tree complete reference, and chapterized reference manual.
A bit of the problem is that the module tree reference is less complete, in comparison to the chapterized manual, which in addition to the full module reference (organized differently) also contains the chapters explaining as much of the datatypes, syntax and the other things one wants in a language manual as we have scraped together so far.
But perhaps "module tree reference" and "chapterized reference" would be an improvement too.
/ Johan Sundström, Lysator
Previous text:
2003-10-21 17:07: Subject: syntax reference and other docs
hi,
when trying to look something up about pike syntax it occured to me that there is no syntax reference. the chapturized reference manual has some of it, but where do i eg find a complete(!) description of eg inherit. ?
just like the module reference a reference for all keywords would be nice.
besides that, the titles module tree quick reference and complete chapterized reference manual are a bit confusing.
the module tree reference isn't exactly quick but rather complete nowadays, while the features of pike have surpassed the chapterized manual making it incomplete.
i'd suggest to change the titles to:
module tree complete reference, and chapterized reference manual.
/ Brevbäraren
but datatypes, syntax and the other things are not modules,
what i meant is that in terms of the title 'module tree' the reference is complete as it does indeed cover all modules and functions.
but those are just nitpicks. it just strikes me odd every time i go over that page.
what would be really nice is to have a manual/reference containing only things that are not in the module tree reference.
pages like http://pike.ida.liu.se/generated/manual/ref/chapter_16.html are not really practical, and i believe all of that is in the module tree anyways.
(still looking for the complete definition of inherit) (maybe it's time for me to apply for cvs access :-)
greetings, martin.
There is a pseudo wiki for the Pike doc on the caudium website at http://caudium.net/developer/pikeref/ex/predef_3A_3A.html and in the chapters. It's not perfect but it's still better than nothing.
/ David Gourdelier
Johan Sundström, Lysator @ Pike developers forum wrote:
A bit of the problem is that the module tree reference is less complete, in comparison to the chapterized manual, which in addition to the full module reference (organized differently) also contains the chapters explaining as much of the datatypes, syntax and the other things one wants in a language manual as we have scraped together so far.
But perhaps "module tree reference" and "chapterized reference" would be an improvement too.
/ Johan Sundström, Lysator
Previous text:
2003-10-21 17:07: Subject: syntax reference and other docs
hi,
when trying to look something up about pike syntax it occured to me that there is no syntax reference. the chapturized reference manual has some of it, but where do i eg find a complete(!) description of eg inherit. ?
just like the module reference a reference for all keywords would be nice.
besides that, the titles module tree quick reference and complete chapterized reference manual are a bit confusing.
the module tree reference isn't exactly quick but rather complete nowadays, while the features of pike have surpassed the chapterized manual making it incomplete.
i'd suggest to change the titles to:
module tree complete reference, and chapterized reference manual.
/ Brevbäraren
pike-devel@lists.lysator.liu.se
-
David Gourdelier -
Johan Sundstr�m, Lysator ＠ Pike developers forum -
Martin Baehr