According to all documentation I've found, a zend_function_entry[] array
should be ended with { NULL, NULL, NULL }, but I've noticed that
_zend_function_entry now has five parts; differences:

-unsigned char *func_arg_types;
+struct _zend_arg_info *arg_info;
+zend_uint num_args;
+zend_uint flags;

Technically, it would make sense to end the array with five NULLs instead
of three, but that doesn't seem to be reflected by
'ext/skeleton/skeleton.c', so I don't know if it's a necessary change or
not.  If it should be changed, I'd also recommend making a macro for the
ending so that this sort of problem won't pop up again in the future, and
it would also make more sense than just having seemingly random NULLs
which could be better described with a macro.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to