Skip to content

Conversation

TimWolla
Copy link
Member

The CHECK_ZVAL_NULL_PATH() macro is unsafe, because it implicitly assumes that the given zval* is IS_STRING.

Based on a GitHub search there does not seem to be any user outside of PHP, all hits were just forks / copies of php-src.

The former is a direct alias of the latter with a more explicit name and the
former is explicitly documented as a “compatibility” alias.
The former is explicitly documented as a “compatibility” alias.
The `CHECK_ZVAL_NULL_PATH()` macro is unsafe, because it implicitly assumes
that the given `zval*` is `IS_STRING`.

Based on a GitHub search there does not seem to be any user outside of PHP, all
hits were just forks / copies of php-src.
Copy link
Member

@nielsdos nielsdos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Never had much trouble with these. However, given that they're compatibility macros and mostly redundant, and that there are no relevant hits, I'm okay with simplifying the API surface.

@TimWolla TimWolla merged commit 6da93a8 into php:master Oct 15, 2025
10 checks passed
@TimWolla TimWolla deleted the zend-has-nul-byte branch October 15, 2025 08:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants