Re: [PHP-DEV] Deprecate PDO::ATTR_ERRMODE [Proposed RFC]

On Tue, 29 Aug 2023 at 14:52, Saki Takamachi wrote: > Hi, internals. > > I thought about various things to improve the current situation where > `PDO::ATTR_ERRMODE` is not working very smartly. > > Exceptions may be thrown regardless of the setting of `PDO::ATTR_ERRMODE`. > https://www.php.net/ma

Re: [PHP-DEV] Deprecate PDO::ATTR_ERRMODE [Proposed RFC]

> However, if we are going to remove it, it would be nice to have this done > consistently across all bundled extensions. Thank you for confirmation. This is probably not technically difficult, but it does increase the scope of change. However, as you say, the specifications should be unified.

Re: [PHP-DEV] Deprecate PDO::ATTR_ERRMODE [Proposed RFC]

>Do you think there is still demand for such error mode control features? > >Personally, I've never seen anyone prefer silent mode, so I think it's worth >making the drastic change. This may be right. There isn't a demand for this in **new** code and I doubt anyone would come forward with a reaso

[PHP-DEV] PASSWORD_DEFAULT value

Hey there, folks! I was wondering here... Is there any reason for `PASSWORD_DEFAULT`'s value not to be `PASSWORD_ARGON2ID`? Would that change require an RFC? -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php

Re: [PHP-DEV] Deprecate PDO::ATTR_ERRMODE [Proposed RFC]

> We may get away with deprecating and removing PDO silent/warning mode because > it's an extension that was introduced in PHP 5 and everyone was on board with > using exception mode. We probably cannot remove silent mode for other > extensions that either mimic older extensions that didn't use

Re: [PHP-DEV] Deprecate PDO::ATTR_ERRMODE [Proposed RFC]

On Wed, Sep 6, 2023, at 2:53 PM, Kamil Tekiela wrote: >>Do you think there is still demand for such error mode control features? >> >>Personally, I've never seen anyone prefer silent mode, so I think it's worth >>making the drastic change. > > This may be right. There isn't a demand for this in **

Re: [PHP-DEV] PASSWORD_DEFAULT value

Hi On 9/6/23 18:08, Vinicius Dias wrote: I was wondering here... Is there any reason for `PASSWORD_DEFAULT`'s value not to be `PASSWORD_ARGON2ID`? To the best of my knowledge Argon2 is not available in a "default" installation of PHP without including any external dependencies. Also Argon2

Re: [PHP-DEV] [RFC] [Discussion] Add 4 new rounding modes to round() function

Hi On 9/5/23 00:34, Jorg Sowa wrote: Introducing a brand-new RoundingMode enum (using union types) I suggested in my first email would nicely solve the naming problem and would also make the API more obvious to use due to stronger typing in the long run. That's also interesting idea and I woul

Re: [PHP-DEV] PASSWORD_DEFAULT value

Argon2 is opt-in, not opt-out, at compile-time, so then we would have to agree on it being acceptable for PASSWORD_DEFAULT to have different values depending on compile-time options, maybe thats completely fine, or maybe it isn't, idk. But as Dusterhus points out, Argon2 is inferior to bcrypt anyw

Re: [PHP-DEV] PASSWORD_DEFAULT value

This is very interesting. It's the first time I see recommendations pro Bcrypt and against Argon2. Even Owasp recommends Argon2 over Bcrypt [1]. I am not a cryptography expert so I believe that if there is a discussion of which one is better PHP shouldn't change things for now, so that totally ans

[PHP-DEV] Re: [RFC] [Discussion] DOM HTML5 parsing and serialization support

> On Sep 4, 2023, at 1:15 PM, Niels Dossche wrote: > > On 04/09/2023 21:54, Dennis Snell wrote: >> Thanks for the proposal Niels, >> >> I’ve dealt with my own grief working through issues in DOMDocument and >> wanting it to work but finding it inadequate. >> >>> HTML5 >> >> This would be a

[PHP-DEV] Re: [RFC] [Discussion] DOM HTML5 parsing and serialization support

Hi Dennis On 06/09/2023 22:02, Dennis Snell wrote: > > >> On Sep 4, 2023, at 1:15 PM, Niels Dossche wrote: >> >> On 04/09/2023 21:54, Dennis Snell wrote: >>> Thanks for the proposal Niels, >>> >>> I’ve dealt with my own grief working through issues in DOMDocument and >>> wanting it to work but

[PHP-DEV] FFI [was: Breakages with rc1]

Hi Peter, Niels, On Tue, Sep 5, 2023 at 3:08 PM Peter Kokot wrote: > > On Tue, 5 Sept 2023 at 11:40, Hanz wrote: >> >> Hello, >> >> Ran into a couple of issues with RC1 that I haven't seen online. >> >> With --with-pear: The --with-pear option is deprecated >> >> With --enable-pear: configure: W

Re: [PHP-DEV] FFI [was: Breakages with rc1]

On Sep 6, 2023, at 19:18, Hanz wrote: > On a totally different note... I'm trying to get my head around FFI > specifically how it could be > used to orchestrate 3rd party pipelines, like those of python. That isn't a particularly good use case for FFI.