Skip to content

PHP: fix ambiguous wording in eval() paragraph #158

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
dingo-d merged 2 commits into from
Feb 8, 2026
Merged

PHP: fix ambiguous wording in eval() paragraph #158

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
49c906b
PHP: fix ambiguous wording in eval() paragraph
rodrigoprimo Feb 4, 2026
68dd6e5
Update wordpress-coding-standards/php.md
rodrigoprimo Feb 6, 2026
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
4 changes: 3 additions & 1 deletion wordpress-coding-standards/php.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -991,7 +991,9 @@ switch ( $foo ) {

The `goto` statement must never be used.

The `eval()` construct is _very dangerous_ and is impossible to secure. Additionally, the `create_function()` function, which internally performs an `eval()`, is deprecated since PHP 7.2 and has been removed in PHP 8.0. Neither of these must be used.
The `eval()` construct is _very dangerous_ and is impossible to secure. It must not be used.

The `create_function()` function internally performs an `eval()`. It was deprecated in PHP 7.2 and removed in PHP 8.0. It must not be used.

### Closures (Anonymous Functions)

Expand Down