Hi!
> implementation. Therefore, I suggest to only add support for an empty
> $escape parameter (PR #3515),
Sounds good.
--
Stas Malyshev
smalys...@gmail.com
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi!
> It's always been bizarre to me that @ can silence fatal errors, which
> has no practical application and makes using @ to silence a lower-level
> error potentially hszardous if its targeted function can also produce a
> fatal error.
Yes, silencing something that kills the script is probably
Hi Nikita,
Nikita Popov wrote:
When the silencing operator @ is used, the intention is generally to
silence expected warnings or notices. However, it currently also silences
fatal errors. As fatal errors also abort request execution, the result will
often be a hard to debug white screen of death
On 02.12.2018 at 21:24, Jakub Zelenka wrote:
> I was wondering if we have got a final list of the top features that will
> be listed in the announcement for the stable release.
>
> Not sure how it's usually selected but thought that it would be good to
> list FPM logging changes that I have been
Hi,
I was wondering if we have got a final list of the top features that will
be listed in the announcement for the stable release.
Not sure how it's usually selected but thought that it would be good to
list FPM logging changes that I have been working on and it's the main
improvement in FPM [1]
On 30.09.2018 at 22:17, Stanislav Malyshev wrote:
>> If we cannot eventually get rid of the escaping for CSV reading (note
>> that I proposed to keep the possibility to use it until PHP *9*), I
>> don't think that we should remove it for CSV writing either, since that
>> would make SplFileObject::
On Sun, 2 Dec 2018, 06:17 Stanislav Malyshev Hi!
>
> I am seeing tons of broken openssl tests on Travis CI. Example:
> https://travis-ci.org/php/php-src/jobs/462367522
>
> All errors seem to be the same:
> 001+ Warning: stream_socket_client(): SSL operation failed with code 1.
> OpenSSL Error mess
On 02/12/2018 09:16, Stanislav Malyshev wrote:
Hi!
I am seeing tons of broken openssl tests on Travis CI. Example:
https://travis-ci.org/php/php-src/jobs/462367522
All errors seem to be the same:
001+ Warning: stream_socket_client(): SSL operation failed with code 1.
OpenSSL Error messages:
002
