On 6/23/2017 5:12 AM, Christopher Jones wrote: > That kind of detail belongs in the RFC. > > A link to existing 'prior art' would have rounded the picture out and let > people decide between alternatives of internal vs external doc. > E.g. link to https://wiki.php.net/internals/references > > Also, is this for core and for extensions? Or for core only? What > about PECL extensions not part of the PHP bundle? > > In summary, see point 8 of > https://blogs.oracle.com/opal/the-mysterious-php-rfc-process-and-how-you-can-change-the-web > > > Chris >
Hi Chris! I agree and if I would have thought about it, I would have included it. (This is not an excuse, just the honest truth.) I can create a follow up RFC with more detailed rules, or maybe we wait a little so that everybody can get acquainted with Doxygen first. Regarding PECL: I clearly state in the introduction "for the C sources of PHP" (in other words, everything inside the php-src repository) and I would stick to that. PECL authors should be allowed, like Composer authors, to do whatever they want. PECL extensions that are to be included in "the C sources of PHP" should of course adopt the style, like it is already today in regards to the code style. Otherwise we can never get to the "future scope" of actually generating docs for browsing. -- Richard "Fleshgrinder" Fussenegger
signature.asc
Description: OpenPGP digital signature
