Re: [PHP-DEV] [RFC] Strict operators directive

Hi, On 10.07.19 23:37, Arnold Daniels wrote: * I also find it somewhat odd that you can't write something like "$obj != null" anymore, only "$obj !== null". To check against null, it's better to use !==. For objects (and resources) using `!= null` is ok, but for other types, it's currently no

Re: [PHP-DEV] [RFC] Strict operators directive

Hi Nikita, Thanks for your feedback. I'll fix the textual errors you mentioned. * "To compare two numeric strings as numbers, they need to be cast to > floats." This may loose precision for integers. It is better to cast to > numbers (int or float) using, with the canonical way being +$x. But I

[PHP-DEV] hebrevc() and other 'contentious' 7.4 proposed deprecations

Two separate topics on this message: First - I wanted to point out that my fierce defense of the hebrev() function does not in fact extend to hebrevc(). As much as I think the RFC was really wrong about hebrev(), and we got scarily close to deprecating a functionality that - while somewhat eso

Re: [PHP-DEV] DKIM on messages

On 2019-07-08 15:57, Tim Düsterhus wrote: This will *still* break anything using DMARC, because neither DKIM nor SPF is valid. Anything *not* using DMARC is better off, though. Ideally the email modifications are disabled entirely. The emails can be reliably detected using the List-Id header

Re: [PHP-DEV] [VOTE] Voting opens for str_starts_with and ends_with functions

> Le 8 juil. 2019 à 18:52, Andrey Andreev a écrit : > > Hi, > > On Mon, Jul 8, 2019 at 4:54 PM Claude Pache > wrote: >> >> >>> Le 8 juil. 2019 à 15:20, Christoph M. Becker a écrit : >>> >>> FTR, there is already substr_compare(). >> >> `substr_compare()` (as