This replaces zend_parse_parameters() with the ZEND_PARSE_PARAMETERS_START/END macros, which provide exception-aware parameter parsing and align the code with modern php-src conventions.

zend_parse_parameters() is also exception aware. And it is not really a modern convention, Fast ZPP got introduced to reduce the overhead of calling ZPP for hot/short functions. Fast ZPP introduces some code bloat into every function, although @ndossche knows more the details about this.

So I'm not sure whether that's really a good motivation here.

I think fast ZPP is indirectly more secure, because null-safety is part of it.

I think fast ZPP is indirectly more secure, because null-safety is part of it.

I don't understand what you mean?

Sorry, I’m confused.

PHP_FUNCTION(my_function)
{
    zend_string *my_str;

    ZEND_PARSE_PARAMETERS_START(1, 1)
        Z_PARAM_STR(my_str)
    ZEND_PARSE_PARAMETERS_END();

    php_printf("String value: '%s'\n", ZSTR_VAL(my_str)); //This value is never NULL
}

I don't see why this is an issue with "old" ZPP? Especially fast ZPP can still have this issue if the parameter is optional.

Thank you