wp_has_noncharacters( string $text ): bool
- Since
- 6.9.0
- Source
wp-includes/utf8.php:158
Description
XML recommends against using noncharacters and HTML forbids their use in attribute names. Unicode recommends that they not be used in open exchange of data.
Noncharacters are code points within the following ranges:
- U+FDD0–U+FDEF
- U+FFFE–U+FFFF
- U+1FFFE, U+1FFFF, U+2FFFE, U+2FFFF, …, U+10FFFE, U+10FFFF
Compatibility
- WordPress
- since 6.9.0
- PHP
- 7.4–8.6-dev
- 6.7.7
- 6.8.8
- 6.9.7
- 7.0.4
- 7.1.0
Present in 3 of the 5 tracked releases, added in 6.9.0, and compiles on PHP 7.4 through 8.6-dev.
Parameters
$textstring- Are there noncharacters in this string?
Return value
bool- Whether noncharacters were found in the string.
Performance profile
How much work a call to wp_has_noncharacters() does, and what it touches: the algorithmic scaling, the Zend instruction count per call across PHP versions, the hooks it hands control to, and the core code that calls it. Measured from the compiled opcodes, not a stopwatch, so every number is identical on any machine running the same PHP version, and every function in core is ranked by cost.
- Cost class
- Trivial
- Scaling
- Constant
- Instructions
- 4
- Plugin surface
- None
- Called by
- 2
Touches nothing outside its own arguments.
No loop in the body: the same number of instructions runs whatever you pass in.
Executed per call on PHP 8.5. The body compiles to 4.
Nothing here hands control to plugin code.
2 places in core call this, so the cost is paid more often than your own code shows.
What one call costs · 1 distinct outcome
One number would be a lie: the work depends on which branch runs. These are every distinct cost wp_has_noncharacters() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
| always | 4 | none |
Across PHP versions
| PHP | Compiled | Executed | Branches | Notes |
|---|---|---|---|---|
| 8.6-dev | 4 | 4 | 0 | |
| 8.5 | 4 | 4 | 0 | |
| 8.4 | 4 | 4 | 0 | 3 fewer instructions than PHP 8.3 |
| 8.3 | 7 | 7 | 0 | |
| 8.2 | 7 | 7 | 0 | |
| 8.1 | 7 | 7 | 0 | |
| 7.4 | 7 | 7 | 0 |
An instruction is not a fixed amount of time, so a matching count is not necessarily the same speed; what it rules out is a difference in the work itself.
Used by · 2
- WP_HTML_Tag_Processor::set_attribute()Updates or creates a new attribute on the currently matched tag with the passed value.
- _wp_has_noncharacters_fallback()Fallback support for determining if a string contains Unicode noncharacters.
Source code
function wp_has_noncharacters( string $text ): bool { /* * Match the UTF-8 byte sequences directly so malformed UTF-8 elsewhere * in the subject does not cause PCRE's Unicode mode to reject the string. */ return 1 === preg_match( '~ # U+FDD0-U+FDEF, U+FFFE-U+FFFF \xEF(?:\xB7[\x90-\xAF]|\xBF[\xBE\xBF]) | # U+nFFFE/U+nFFFF (?:\xF0[\x9F\xAF\xBF]|[\xF1-\xF3][\x8F\x9F\xAF\xBF]|\xF4\x8F)\xBF[\xBE\xBF] ~x', $text );}Changelog
Introduced in 6.9.0. Unchanged from 6.9.7 through 7.1.0.
Signature, return type and hooks compared across 3 parsed releases.
About this page
- Parsed data
- Generated from the wordpress-develop 7.1.0 tag, from
src/wp-includes/utf8.php, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it. - Corrections
- Something wrong on this page? Report it and it gets fixed in the next regeneration.