Hey Dustin,
Given the amount of use-cases (very low, so far) this feels much much
easier if just implemented in userland via `Closure::call()`, since the
scope of the patch complicates the class model of PHP by a whole lot.
Another simple solution is to use things such as leedavis81/altr-ego, whi
On Thu, Sep 21, 2017 at 1:43 PM, Christoph M. Becker wrote:
> I don't think the current behavior is a bug, but rather the escape
> character is an extension to the CSV "standard" (RFC 7111).
Are you sure you mean RFC 7111 ?
I was just parrotting the number in my previous email, but now I
looked i
On Thu, Sep 21, 2017 at 11:08 PM, Dan Ackroyd wrote:
> On 21 September 2017 at 12:43, Christoph M. Becker wrote:
>> Hi everybody!
>>
>> There are several bug reports regarding "broken" fputcsv() behavior in
>> our tracker, namely, because the $escape parameter causes unexpected
>> results. For i
Hi!
Almost two years ago, I opened discussion regarding my proposal to support
class friendship through a new keyword, `friend`. For a number of reasons
(mostly work-related; some personal) I didn't have time to move the process
forward. There were several hot-topic discussions going through the m
On Thu, Sep 21, 2017 at 3:13 PM, Stanislav Malyshev wrote:
> Hi!
>
>> After discussion with Levi and others who suggested a simpler
>> approach, I'd like to offer
>> https://github.com/php/php-src/compare/master...sgolemon:pipe2 as an
>> alternate possibility.
>
> I am still feeling it is a bit we
Hi!
> After discussion with Levi and others who suggested a simpler
> approach, I'd like to offer
> https://github.com/php/php-src/compare/master...sgolemon:pipe2 as an
> alternate possibility.
I am still feeling it is a bit weird to do things that way, but other
than that (which is just my perso
On 21 September 2017 at 12:43, Christoph M. Becker wrote:
> Hi everybody!
>
> There are several bug reports regarding "broken" fputcsv() behavior in
> our tracker, namely, because the $escape parameter causes unexpected
> results. For instance:
I looked at fixing some of the CSV related bugs ab
Hi everyone,
Something I've long wanted in PHP has been built-in versions of some
common functional primitives, functions that operate on functions and
create new functions for you. I've finally gotten round to bringing this
up because my operator functions RFC could really benefit from them.
On 21 September 2017 18:32:57 BST, Andreas Hennings wrote:
>So empty string would enable the standard behavior RFC 7111 with no
>escape char.
>If so, I support this.
Just a note regarding standards: please make sure the behaviour of common
applications, most notably Excel, is considered and test
So empty string would enable the standard behavior RFC 7111 with no escape char.
If so, I support this.
I don't know if '' or true / false / null should be this "special value".
It has to be something that was not legal before, and that people
should use intentionally and not by accident.
I guess
On Thu, Sep 21, 2017 at 12:28 PM, Fleshgrinder wrote:
> I also hope to see some progress on the C+PHP front.
>
+1 all over this and up in its business.
-Sara
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hey Internals!
The UUID RFC [1] was now officially declined.
Some of you might ask themselves what's going to happen next. Well, I
will most probably move it to PECL after a little overhaul where I
incorporate the latest feedback I got on the PR. After that I also hope
to see some progress on the
Am 21.09.2017 um 16:52 schrieb Sara Golemon:
On Thu, Sep 21, 2017 at 10:47 AM, li...@rhsoft.net wrote:
Am 21.09.2017 um 16:36 schrieb Remi Collet:
Le 21/09/2017 à 16:12, li...@rhsoft.net a écrit :
curent 7.1 HEAD - guys sleep() can't replace usleep(1) becaus eit's a
million times longer
us
On Thu, Sep 21, 2017 at 10:47 AM, li...@rhsoft.net wrote:
> Am 21.09.2017 um 16:36 schrieb Remi Collet:
>> Le 21/09/2017 à 16:12, li...@rhsoft.net a écrit :
>>> curent 7.1 HEAD - guys sleep() can't replace usleep(1) becaus eit's a
>>> million times longer
>>>
>>> usleep: warning: usleep(1) is depr
Am 21.09.2017 um 16:36 schrieb Remi Collet:
Le 21/09/2017 à 16:12, li...@rhsoft.net a écrit :
curent 7.1 HEAD - guys sleep() can't replace usleep(1) becaus eit's a
million times longer
usleep: warning: usleep(1) is deprecated, and will be removed in near
future!!
usleep: warning: use sleep(1)
Le 21/09/2017 à 16:12, li...@rhsoft.net a écrit :
> curent 7.1 HEAD - guys sleep() can't replace usleep(1) becaus eit's a
> million times longer
>
> usleep: warning: usleep(1) is deprecated, and will be removed in near
> future!!
> usleep: warning: use sleep(1) instead...
>
usleep is NOT deprec
curent 7.1 HEAD - guys sleep() can't replace usleep(1) becaus eit's a
million times longer
usleep: warning: usleep(1) is deprecated, and will be removed in near
future!!
usleep: warning: use sleep(1) instead...
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: htt
Hi everybody!
There are several bug reports regarding "broken" fputcsv() behavior in
our tracker, namely, because the $escape parameter causes unexpected
results. For instance:
outputs
"a\"",bbb
instead of the expected
"a\""",bbb
I don't think the current behavior is a bug, but
18 matches
Mail list logo
