Page Menu
Home
Phorge
Search
Configure Global Search
Log In
Files
F2681163
D25108.1734637603.diff
No One
Temporary
Actions
View File
Edit File
Delete File
View Transforms
Subscribe
Award Token
Flag For Later
Advanced/Developer...
View Handle
View Hovercard
Size
4 KB
Referenced Files
None
Subscribers
None
D25108.1734637603.diff
View Options
diff --git a/src/docs/contributor/php_coding_standards.diviner b/src/docs/contributor/php_coding_standards.diviner
--- a/src/docs/contributor/php_coding_standards.diviner
+++ b/src/docs/contributor/php_coding_standards.diviner
@@ -176,3 +176,7 @@
return $this->favoriteFood;
}
}
+
+# Extra Readings
+
+* @{article:PHP Pitfalls}
diff --git a/src/docs/flavor/php_pitfalls.diviner b/src/docs/flavor/php_pitfalls.diviner
--- a/src/docs/flavor/php_pitfalls.diviner
+++ b/src/docs/flavor/php_pitfalls.diviner
@@ -49,18 +49,7 @@
false // boolean
array() // empty array
-Disregarding some bizarre edge cases, all other values are truthy. Note that
-because "0" is falsey, this sort of thing (intended to prevent users from making
-empty comments) is wrong in PHP:
-
- COUNTEREXAMPLE
- if ($comment_text) {
- make_comment($comment_text);
- }
-
-This is wrong because it prevents users from making the comment "0". //THIS
-COMMENT IS TOTALLY AWESOME AND I MAKE IT ALL THE TIME SO YOU HAD BETTER NOT
-BREAK IT!!!// A better test is probably `strlen()`.
+Disregarding some bizarre edge cases, all other values are truthy.
In addition to truth tests with `if`, PHP has two special truthiness operators
which look like functions but aren't: `empty()` and `isset()`. These operators
@@ -92,16 +81,16 @@
`empty()` evaluates truthiness exactly opposite of `if()`. `isset()` returns
`true` for everything except `null`. This is the truth table:
-| Value | `if()` | `empty()` | `isset()` |
-|-------|--------|-----------|-----------|
-| `null` | `false` | `true` | `false` |
-| `0` | `false` | `true` | `true` |
-| `0.0` | `false` | `true` | `true` |
-| `"0"` | `false` | `true` | `true` |
-| `""` | `false` | `true` | `true` |
-| `false` | `false` | `true` | `true` |
-| `array()` | `false` | `true` | `true` |
-| Everything else | `true` | `false` | `true` |
+| Value | `if()` | `empty()` | `isset()` |
+|---------------|--------|-----------|-----------|
+| `null` | `false`| `true` | `false` |
+| `0` | `false`| `true` | `true` |
+| `0.0` | `false`| `true` | `true` |
+| `"0"` | `false`| `true` | `true` |
+| `""` | `false`| `true` | `true` |
+|`false` | `false`| `true` | `true` |
+|`array()` | `false`| `true` | `true` |
+|Everything else| `true` | `false` | `true` |
The value of these operators is that they accept undeclared variables and do
not issue a warning. Specifically, if you try to do this you get a warning:
@@ -138,6 +127,70 @@
are testing something that may not be declared. Use `empty()` if you want to
type `if (!$value)` but you are testing something that may not be declared.
+= Check for non-empty strings =
+
+As already mentioned, note that you cannot just use an `if` or `empty()` to
+check for a non-empty string, mostly because "0" is falsey, so you cannot rely
+on this sort of thing to prevent users from making empty comments:
+
+ COUNTEREXAMPLE
+ if ($comment_text) {
+ make_comment($comment_text);
+ }
+
+This is wrong because it prevents users from making the comment "0".
+
+//THE COMMENT "0" IS TOTALLY AWESOME AND I MAKE IT ALL THE TIME SO YOU HAD
+BETTER NOT BREAK IT!!!//
+
+Another way //was// also `strlen()`:
+
+ COUNTEREXAMPLE
+ if (strlen($comment_text)) {
+ make_comment($comment_text);
+ }
+
+But `strlen()` wastes too many CPU cycles to just check of a non-empty
+string, and, `strlen()` also comes with these funny things:
+
+| Check | Return |
+|-----------------|--------|
+| `strlen(false)` | `0` |
+| `strlen(true)` | `1` |
+| `strlen(null)` | deprecation exception since PHP 8.1 |
+
+In short, outside Phorge, this is the general thing to check for non-empty strings
+for most wild input types:
+
+```lang=php
+ $value_str = (string) $value;
+ if ($value_str !== '') {
+ // do something
+ }
+```
+
+In Phorge, a better and safer approach is this one:
+
+```lang=php
+ $value_str = phutil_string_cast($value);
+ if ($value_str !== '') {
+ // do something
+ }
+```
+
+But, in Phorge, if you are 100% sure that you are only working with string and null,
+adopt this instead:
+
+```lang=php
+ if (phutil_nonempty_string($value)) {
+ // do something
+ }
+```
+
+WARNING: The function `phutil_nonempty_string()` is designed to throw an exception
+if it receives `true`, `false`, an array, an object or anything alien that is not
+a string and not null. Do your evaluations but probably this is what you want.
+
= usort(), uksort(), and uasort() are Slow =
This family of functions is often extremely slow for large datasets. You should
File Metadata
Details
Attached
Mime Type
text/plain
Expires
Thu, Dec 19, 19:46 (19 h, 11 m)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
1015451
Default Alt Text
D25108.1734637603.diff (4 KB)
Attached To
Mode
D25108: PHP Pitfalls: mention strlen() deprecation since PHP 8.1
Attached
Detach File
Event Timeline
Log In to Comment