4 ms·

PSR-0 is widely adopted by anything relevant in the PHP ecosystem. Sure, those style guides might not be pitch-perfect but it is time for PHP to step it up and

PSR-0 is widely adopted by anything relevant in the PHP ecosystem. Sure, those style guides might not be pitch-perfect but it is time for PHP to step it up and get some uniformity in their codebase. _At least_ adopting PSR-0 would have been a great step towards that. Uncertain why I am getting downvoted for this (top parent) it is my personal opinion and just because you think otherwise isn't a valid reason.

ceejayoz 13y ago
Why would you expect a C project to use a PHP style guide?
wvenable 13y ago
How does the PHP project adopt PSR-0? PSR-0 is a standard for programs written in PHP; what would they do to adopt it that is in anyway better than the current situation?
- tmzt 13y ago
  Part of PSR-0 is a standard for autoloading namespaced classes, so, if you write you're own autoloader, implementing PSR-0 is neccessary to support loading libraries using that standard. The situation before PSR-0 was a mess of different, incompatible directory layouts for loadable libraries.
McGlockenshire 13y ago
> At least adopting PSR-0 would have been a great step towards that. PSR-0 is broken on machines using filesystems that aren't completely case-sensitive. Implementing PSR-0 also takes about five lines of code. Sure, it's more boilerplate, but it's not something that needs to be in core.
PeeHaa 13y ago
If you don't know what you are talking about please stop. What does PSR-x have to do with core? Besides the fact that PSR-0 is broken it doesn't really make sense to expect anything of it in core. PSR-x are some "rules" made up by some creators of frameworks / projects to aid in userland CS / directory structure decisions and please note that not everybody agrees on what they think people should do.
lonnyk 13y ago
PSR-0 doesn't really apply to C code. Also, php-src has had coding standards that really haven't changed for years: https://github.com/php/php-src/blob/master/CODING_STANDARDS https://github.com/php/php-src/blob/master/CODING_STANDARDS

ceejayoz 13y ago

Why would you expect a C project to use a PHP style guide?

wvenable 13y ago

How does the PHP project adopt PSR-0? PSR-0 is a standard for programs written in PHP; what would they do to adopt it that is in anyway better than the current situation?

tmzt 13y ago
Part of PSR-0 is a standard for autoloading namespaced classes, so, if you write you're own autoloader, implementing PSR-0 is neccessary to support loading libraries using that standard. The situation before PSR-0 was a mess of different, incompatible directory layouts for loadable libraries.

McGlockenshire 13y ago

> At least adopting PSR-0 would have been a great step towards that. PSR-0 is broken on machines using filesystems that aren't completely case-sensitive. Implementing PSR-0 also takes about five lines of code. Sure, it's more boilerplate, but it's not something that needs to be in core.

PeeHaa 13y ago

If you don't know what you are talking about please stop. What does PSR-x have to do with core? Besides the fact that PSR-0 is broken it doesn't really make sense to expect anything of it in core. PSR-x are some "rules" made up by some creators of frameworks / projects to aid in userland CS / directory structure decisions and please note that not everybody agrees on what they think people should do.

lonnyk 13y ago

PSR-0 doesn't really apply to C code. Also, php-src has had coding standards that really haven't changed for years: https://github.com/php/php-src/blob/master/CODING_STANDARDS https://github.com/php/php-src/blob/master/CODING_STANDARDS