Doc #80060 [Opn->Sus]: Use PSR coding guidelines in PHP.net docs (instead of PEAR-CS)
Edit report at https://bugs.php.net/bug.php?id=80060&edit=1
ID: 80060
Updated by: requinix@php.net
Reported by: t dot motylewski at gmail dot com
Summary: Use PSR coding guidelines in PHP.net docs (instead
of PEAR-CS)
-Status: Open
+Status: Suspended
Type: Documentation Problem
Package: Documentation problem
PHP Version: Irrelevant
Block user comment: N
Private report: N
New Comment:
The PSRs are unofficial community-written guidelines for interoperability between frameworks and
projects. If PHP were to follow their guidelines then that could be interpreted as an endorsement -
reasoning that extends to other areas, such as why php.net does not employ a popular framework.
Whether or not to continue that philosophy is beyond the scope of this bug tracker and would need to
be discussed internally through the mailing list.
https://www.php.net/mailing-lists.php
Previous Comments:
------------------------------------------------------------------------
[2020-09-04 12:25:45] t dot motylewski at gmail dot com
Description:
------------
Right now (as stated here: http://doc.php.net/tutorial/style.php) the code
style used in PHP documentation is PEAR-CS https://pear.php.net/manual/en/coding-standards.php
PEAR-CS covers much less of the PHP language capabilities than PSR-1,2,12, it has much smaller
adoption and PEAR in general looks unmaintained.
I suggest that the new coding standard for PHP docs should be PSR.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=80060&edit=1
Thread (4 messages)