psr-2

【推荐】2019 Java 开发者跳槽指南.pdf(吐血整理) >>> 本篇规范是 PSR-1 基本代码规范的继承与扩展。 本规范希望通过制定一系列规范化PHP代码的规则，以减少在浏览不同作者的代码时，因代码风格的不同而造成不便。 当多名程序员在多个项目中合作时，就需要一个共同的编码规范， 而本文中的风格规范源自于多个不同项目代码风格的共同特性， 因此，本规范的价值在于我们都遵循这个编码风格，而不是在于它本身。 关键词 “必须”("MUST")、“一定不可/一定不能”("MUST NOT")、“需要”("REQUIRED")、 “将会”("SHALL")、“不会”("SHALL NOT")、“应该”("SHOULD")、“不该”("SHOULD NOT")、 “推荐”("RECOMMENDED")、“可以”("MAY")和”可选“("OPTIONAL")的详细描述可参见 [RFC 2119][] 。 1. 概览 代码 必须 遵循 PSR-1 中的编码规范 。 代码 必须 使用4个空格符而不是 tab键 进行缩进。 每行的字符数 应该 软性保持在80个之内， 理论上 一定不可 多于120个， 但 一定不能 有硬性限制。 每个namespace命名空间声明语句和use声明语句块后面， 必须 插入一个空白行。 类的开始花括号({) 必须 写在函数声明后自成一行，结束花括号(})也 必须

What is allowed between these two: $value = 'value'; $user = 'John'; $timestamp = 1480927909; $day = date('Y-m-d', $timestamp); or $value = 'value'; $user = 'John'; $timestamp = 1480927909; $day = date('Y-m-d', $timestamp); PSR-2 does not have specific rules for this kind of inter-line alignment: From the PSR-2 Conclusion : There are many elements of style and practice intentionally omitted by this guide . These include but are not limited to: Declaration of global variables and global constants Declaration of functions Operators and assignment Inter-line alignment Comments and documentation

Question: are parentheses required in PSR-2 PHP ternary syntax? Looking for which (if either) of the following ternary statement's syntax is compliant with PSR-2 - I also need to be pointed to documentation or some authority link: $error = ($error_status) ? 'Error' : 'No Error'; OR $error = $error_status ? 'Error' : 'No Error'; Note: php.net it shows the syntax with the parentheses, but I could not find this in any of the 'official PSR-2' docs. Conclusion If there is no PSR-2 standard on this, which way is the most common convention? The PSR-2 standard specifically omits any opinion on