Re: Call for a doc push
| From: | Gwynne Raskind | Date: | Sun, 21 Jun 2009 14:27:25 +0000 |
| Subject: | Re: Call for a doc push | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-44392@lists.php.net to get a copy of this message | ||
On Jun 21, 2009, at 6:23 AM, zoe wrote:
Zoe, have a look at <http://news.php.net/php.doc.cvs/4180> :). I don't have anything that can read that ODP file you linked (at least, not in any useful sense), but the opcodes.html file is all there. With any luck, someone else will come along and clean it up a bit, and/or expand on it. -- GwynneGuys and gals, in the old days we had a very close tie between the code and the documentation. As the project has grown the two have drifted apart. I think this is mostly because the phpdoc team has done an amazing job keeping up with the code changes and writing awesome documentation. This has made us a bit lazy and complacent. I would like to encourage everyone on this list to spend a little bit of time looking at the parts of the documentation that cover things you are familiar with. Or even just going through some of the doc bugs and helping out in general.This reminded me that a while ago I made some opcode documentation available in the form of a set of charts written by Andy Wharmby (http://www.zapt.info/PHPOpcodes_Sep2008.odp) and some opcode samples (http://www.zapt.info/opcodes.html) from the IBM Japan team. I don't think either of these ever made it the PHP docs and as they are still on my personal website and they are somewhat at risk :-/ I heard recently that people were using them (http://tr.im/phpcompilerinternals) so I'd like to put them somewhere more permanent. My current plan is to move them both to sp1.php.net. Does anyone object? Or better still would anyone be willing to integrate them with the PHP docs?