RE: External Message: [PHP-DEV] Re: [VOTE] Static class

This was my first RFC so understandably I was somewhat emotionally invested in it, even though the significance of the feature was low. Along the way I learned a lot and met many new people whom inspired me to complete this work. One of the PHPF members even said to me, "I think you did a good j

RE: External Message: Re: [PHP-DEV] PDO subclass names

> > This would allow people to use MariaDB and MySQL-specific functionality by > using the respective driver namespace and remove any confusion about if this > works with both or only one of them. > > > > I know it seems to be out of scope, but this deals with PDO subclass names > and this seems to

RE: External Message: Re: [PHP-DEV] [RFC][Vote announcement] Property hooks

> On Wed, Apr 10, 2024 at 4:01 PM Erick de Azevedo Lima > wrote: > Maybe if such a feedback was given before and it was decided to go for a > trimmed version of the feature, maybe Ilija/Larry could have had less work to > implement and test all the variantes the

RE: External Message: Re: [PHP-DEV] What's up with emails?

> Gmail is rejecting emails after we moved the servers without telling us why, > in > enough detail to do anything about it. It's not just gmail. -Jeff

RE: External Message: [PHP-DEV] What's up with emails?

I had an email to the list bounce due to SpamCop adding a sizeable portion of Outlook's IP space into a block (as they've been erroneously doing for 25 years now). Emailed syst...@php.net about it, never heard back. I'm also receiving next-to-no list traffic and receiving similar bounce message

RE: [PHP-DEV] RFC proposal: worker mode primitives for SAPIs

> > Again, the representation as objects isn't a key requirement. Python's > > WSGI spec simply has a dictionary (read: associative array) of the > > environment based on CGI. The application might well turn that into a > > more powerful object, but standardisation of such wasn't considered a > > p

RE: [PHP-DEV] Filesystem path APIs

> The feature request is about the following: > We already have some functions to work with paths in PHP, e.g. basename, > dirname, realpath. > We do not have some common path APIs that you can find in other languages > like: path_join to join paths and path_normalize to normalize paths. ... > Wha

RE: [PHP-DEV] [PDO] 2 phase commit

> Hi internals, > > For the past few days I've been thinking about whether to make a suggestion > to add two-phase commit functionality to pdo. > > I would like to hear everyone's opinions. Hello, Would the implementation use the underlying RDBMS two-phase commit? Or would the proposal be to t

RE: [PHP-DEV] Expose pdo_parse_params to userspace

> I have to say I am not a fan of this proposal. While definitely a super nice > feature in PDO, it's more of a hack rather than proper feature. > Certain RDBMSs support named parameters in prepared statements, but > MySQL doesn't. Therefore, the solution implemented in PDO is a hack. It's very >

RE: [PHP-DEV] [RFC] [Discussion] Adding bcround, bcfloor and bcceil to BCMath

> -Original Message- > Still, I think that there may be cases where calculation functions like > mainframe > BCD are required, such as when calculating money. We use BCMath for money calculations. -Jeff -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https

Re: [PHP-DEV] Planning ahead, will 8.5 exist and major version decisions (was: Deprecate functions with overloaded signatures)

> [2] I am sure lots of userland people and other people will have >opinions also. I just don't think they will be as insightful or useful >in this conversation. Userland here and I agree with you completely. My opinion is that the maintainers should decide, since they bear the burden of the deci

RE: [PHP-DEV] [RFC] Property hooks, nee accessors

> Ilija Tovilo and I would like to offer another RFC for your consideration. > It's > been a while in coming, and we've evolved the design quite a bit just in the > last > week so if you saw an earlier draft of it in the past few months, I would > encourage you to read it over again to make sure

RE: [PHP-DEV] Future stability of PHP?

Essentially the same thing here. Removal of dynamic properties will be the next big one for my team. It's the deprecations that hit huge swaths of code without really offering much benefit that are annoying. Yes, we have a _lot_ of classes. Also multiple versions of Zend framework that we backp

RE: [PHP-DEV] Future stability of PHP?

Essentially the same thing here. Removal of dynamic properties will be the next big one for my team. It's the deprecations that hit huge swaths of code without really offering much benefit that are annoying. -Jeff You can add `#[AllowDynamicProperties]` to classes where you want to allow dynam

RE: [PHP-DEV] Future stability of PHP?

> So turn off the deprecation warnings for now. They're just a heads up that > behaviour is going to change in the future, with PHP 9. > > I doubt you'd prefer not to be aware of the change well in advance. Oh, absolutely. We run those "on" in our dev and QA environments but off in production. I

RE: [PHP-DEV] Future stability of PHP?

> was something introduced in a time that the code being written using it has > 100% test coverage and static analysers protecting it. It's easier for me to > deal > with any BC breaks of PHP 7.1 or higher than it is to deal with deprecations > of > PHP 5.6 or lower. Essentially the same thing h

RE: [PHP-DEV] [VOTE] Improve unserialize() error handling

> a) "Add the \UnserializationFailedException and wrap any Throwables in PHP > 8.x?" > > This proposal was declined with 20 (Yes) to 12 (No) Votes (62.5%). > > b) "Increase the severity of emitted E_NOTICE to E_WARNING in PHP 8.x?" > > This proposal was accepted with 33 (Yes) to 2 (No) Votes (94

RE: [PHP-DEV] RFC json_validate() - status: Under Discussion

> -Original Message- > From: juan carlos morales > Sent: Thursday, August 25, 2022 12:02 PM > To: PHP Internals List > Subject: [PHP-DEV] RFC json_validate() - status: Under Discussion > > Hello. > > I am glad to present to you the RFC for json_validate() function. > > The code/impleme

RE: [PHP-DEV] [RFC] Exception type hint

> -Original Message- > From: Larry Garfield > Sent: Wednesday, June 29, 2022 12:39 PM > To: php internals > Subject: Re: [PHP-DEV] [RFC] Exception type hint > > On Wed, Jun 29, 2022, at 10:42 AM, Guilliam Xavier wrote: > > Hi (note: your message was flagged as spam), > > > >> https://git

RE: [PHP-DEV] [RFC] [Under Discussion] New Curl URL API

Hello Pierrick, A thin wrapper would be the most flexible. Someone can always write a "friendlier" class using your thin wrapper, as you mentioned, but one cannot easily go the other direction. -Jeff -Original Message- From: Pierrick Charron Sent: Friday, June 24, 2022 9:49 AM To: L