Hello internals,
While working on analysing the impact of the changes proposed by amending
the behaviour of the increment and decrement operators (
https://wiki.php.net/rfc/saner-inc-dec-operators) I discovered that the
range() function has some rather lax behaviour that is very unintuitive.
I
On Mon, Mar 27, 2023, at 2:12 PM, Mel Dafert wrote:
> On 27 March 2023 20:20:58 CEST, "Michał Marcin Brzuchalski"
> wrote:
>> Personally, I'd like the unserialize to throw an exception if trailing
>>bytes are detected.
>>If not by default then with the use of the option passed to unserialize
On 27 March 2023 20:20:58 CEST, "Michał Marcin Brzuchalski"
wrote:
> Personally, I'd like the unserialize to throw an exception if trailing
>bytes are detected.
>If not by default then with the use of the option passed to unserialize
>function.
If that's the desired direction, it makes more
Hi Tim,
thanks for the RFC
pon., 27 mar 2023 o 19:04 Tim Düsterhus napisał(a):
> Hi
>
> I'm now opening discussion for the RFC "Make unserialize() emit a
> warning for trailing bytes":
>
>
>
> RFC: Make unserialize() emit a warning for trailing bytes
>
Hi
I'm now opening discussion for the RFC "Make unserialize() emit a
warning for trailing bytes":
RFC: Make unserialize() emit a warning for trailing bytes
https://wiki.php.net/rfc/unserialize_warn_on_trailing_data
Proof of concept implementation is in:
