Skip to content

Adds General section with notation of PSR-2 usage on Keywords and True/F... #38

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 22, 2013
Merged

Adds General section with notation of PSR-2 usage on Keywords and True/F... #38

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions manual/en-US/coding-standards/chapters/php.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,16 @@ For files that contain only PHP code, the closing tag (`?>`) should not be inclu

Files should always end with a blank new line.

### General

Pursuant to PSR-2 [Keywords and True/False/Null][]

> PHP [keywords][] MUST be in lower case.
> The PHP constants `true`, `false`, and `null` MUST be in lower case.

[Keywords and True/False/Null]: https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md#25-keywords-and-truefalsenull
[keywords]: http://php.net/manual/en/reserved.keywords.php

### Including Code

Anywhere you are unconditionally including a file, use `require_once`. Anywhere you are conditionally including a file (for example, factory methods), use `include_once`. Either of these will ensure that files are included only once. They share the same file list, so you don't need to worry about mixing them. A file included with `require_once` will not be included again by `include_once`.
Expand Down