Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82222 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 37672 invoked from network); 9 Feb 2015 04:48:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Feb 2015 04:48:25 -0000 X-Host-Fingerprint: 195.225.93.162 195225093162.olsztyn.vectranet.pl Received: from [195.225.93.162] ([195.225.93.162:19462] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 98/C5-26926-81C38D45 for ; Sun, 08 Feb 2015 23:48:24 -0500 To: internals@lists.php.net,phpdev@ehrhardt.nl Message-ID: <54D83C15.4010104@php.net> Date: Mon, 09 Feb 2015 05:48:21 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 References: <54D3EE95.2080109@lerdorf.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 195.225.93.162 Subject: Re: Annotated PHP 5->7 extension diff From: sobak@php.net (Maciej Sobaczewski) Hello Jan, > An annotated diff would be very welcome! But more or less complete > documentation as well. > > Jan > What about placing such informations in the section of PHP manual like http://php.net/manual/en/internals2.php (for ZE3, of course). I suspect that writing regular text files in repo or updating page on the wiki is faster, but, well, I also think that's what we have documentation for. It would also allow us to remove some documentation files from php-src, like: - README.EXT_SKEL - README.NEW_OUTPUT_API - README.PARAMETERS_PARSING_API - README.STREAMS - README.TESTING - README.TESTING2 - README.UNIX-BUILD-SYSTEM - README.WIN32-BUILD-SYSTEM - README.input_filter - README.namespaces or even guidelines for developers such as coding standards, release process etc. We have many informations, which can live in more suitable place, IMO. I'm totally aware that those files are tend to be more up-to-date thanks to placing them directly where core developers work. However, we have wiki pages for internals stuff, so why not move it to the manual and provide better "Zend Hacker's Guide"? There were some complaints about its incompleteness and creation of Zend Engine 3 is a great opportunity to fix it. I know that you don't have much time - core development is much more important and it's understandable, but please consider this proposal. I can help with directly porting files mentioned above and changes for ZE3 from wiki and UPGRADING.INTERNALS if it will help somehow. If so, be aware that I don't have skills to check its meritorical correctness, though. Regards, Maciej.