Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44392 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 66882 invoked from network); 21 Jun 2009 14:27:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Jun 2009 14:27:31 -0000 Authentication-Results: pb1.pair.com header.from=gwynne@darkrainfall.org; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=gwynne@darkrainfall.org; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain darkrainfall.org from 208.97.132.207 cause and error) X-PHP-List-Original-Sender: gwynne@darkrainfall.org X-Host-Fingerprint: 208.97.132.207 caiajhbdccah.dreamhost.com Received: from [208.97.132.207] ([208.97.132.207:53249] helo=homiemail-a4.g.dreamhost.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5E/4F-09016-1534E3A4 for ; Sun, 21 Jun 2009 10:27:30 -0400 Received: from Moonstar.home (pool-71-174-84-161.bstnma.fios.verizon.net [71.174.84.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by homiemail-a4.g.dreamhost.com (Postfix) with ESMTP id 7726441695; Sun, 21 Jun 2009 07:27:26 -0700 (PDT) Cc: PHP Developers Mailing List Message-ID: <2308C596-45DC-433C-BB7B-2889E28142DC@darkrainfall.org> To: zoe In-Reply-To: <4A3E0A1B.3080305@googlemail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Sun, 21 Jun 2009 10:27:25 -0400 References: <4A3BBF03.5050207@lerdorf.com> <4A3E0A1B.3080305@googlemail.com> X-Mailer: Apple Mail (2.935.3) Subject: Re: [PHP-DEV] Call for a doc push From: gwynne@darkrainfall.org (Gwynne Raskind) On Jun 21, 2009, at 6:23 AM, zoe wrote: >> Guys 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? Zoe, have a look at :). 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. -- Gwynne