Re: [PHP-DEV] Windows builds of PHP 7.4+ use Visual Studio 2019

Apache server VS16 builds at https://www.apachelounge.com/download/ Christoph M. Becker wrote: > Hi, > > I like to inform you, that the official Windows builds of PHP 7.4 and > master (available from windows.php.net; currently only snapshot builds, > of course) are done with Visual Studio 201

Re: [PHP-DEV] Handling of null arguments to internal functions

On Thu, 6 Jun 2019 at 12:49, Arvids Godjuks wrote: > consistency, in general, would be a nice change of pace so you don't have > to keep in mind that there are slight differences in behaviour depending on > what you call - a built-in function or a userland one. > This is my view as well. Anothe

[PHP-DEV] Disabling arginfo argument type checks for internal functions

Hi internals, I plan to disable the checking of arginfo argument types for internal functions in https://github.com/php/php-src/pull/4232 (PHP 8 only). This is necessary to avoid duplicate type checks in both arginfo and zpp. Once this lands, PRs to add arginfo types (available through reflection)

[PHP-DEV] Windows builds of PHP 7.4+ use Visual Studio 2019

Hi, I like to inform you, that the official Windows builds of PHP 7.4 and master (available from windows.php.net; currently only snapshot builds, of course) are done with Visual Studio 2019. While it is still possible to build these PHP versions with Visual Studio 2017, this is no longer tested.

Re: [PHP-DEV] Handling of null arguments to internal functions

чт, 6 июн. 2019 г. в 10:55, Nikita Popov : > Hi internals, > > The https://wiki.php.net/rfc/consistent_type_errors RFC resolved one of > the > big differences in argument handling between internal and userland > functions. This change allowed us to add return type information (available > through

Re: [PHP-DEV] Handling of null arguments to internal functions

On Thu, Jun 6, 2019 at 12:10 PM Côme Chilliet wrote: > I’m not sure if this is exactly the same topic, but one problem I have > with how internal functions are handling arguments is how the absence of an > optional argument is treated. > > I have stumbled across functions documented as functionna

Re: [PHP-DEV] Handling of null arguments to internal functions

On Thu, 6 Jun 2019 at 10:54, Nikita Popov wrote: > Hi internals, > > The https://wiki.php.net/rfc/consistent_type_errors RFC resolved one of > the > big differences in argument handling between internal and userland > functions. This change allowed us to add return type information (available > t

Re: [PHP-DEV] Handling of null arguments to internal functions

I’m not sure if this is exactly the same topic, but one problem I have with how internal functions are handling arguments is how the absence of an optional argument is treated. I have stumbled across functions documented as functionname($arg1, $arg2 = NULL) which behaves differently when called

[PHP-DEV] Handling of null arguments to internal functions

Hi internals, The https://wiki.php.net/rfc/consistent_type_errors RFC resolved one of the big differences in argument handling between internal and userland functions. This change allowed us to add return type information (available through reflection) to internal functions, something that Gabriel

Re: [PHP-DEV] Add get_mangled_object_properties()

Provided feedback on the patch: looking good for me, not sure of this needs an RFC or not. On Thu, Jun 6, 2019, 09:53 Nikita Popov wrote: > On Tue, May 14, 2019 at 4:45 PM Nikita Popov wrote: > >> On Tue, May 14, 2019 at 4:37 PM Marco Pivetta wrote: >> >>> >>> On Tue, May 14, 2019 at 4:29 PM B

Re: [PHP-DEV] Add get_mangled_object_properties()

On Tue, May 14, 2019 at 4:45 PM Nikita Popov wrote: > On Tue, May 14, 2019 at 4:37 PM Marco Pivetta wrote: > >> >> On Tue, May 14, 2019 at 4:29 PM Benjamin Morel >> wrote: >> >>> I like the explicitness of the proposal, but only if performance is as >>> good >>> as (array) cast. One of the reas