Hello,
I'm Damian (wiki username D0niek), I want to write RFC about function
overloading and of course help with other RFC by commenting how I see it
should works.
--
Pozdrawiam, Damian
o^
Results for project PHP master, build date 2017-04-12 11:42:46-07:00
commit: fd0e71d
previous commit:07fe861
revision date: 2017-04-11 15:08:05-07:00
environment:Haswell-EP
cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores,
stepping 2, LLC 45 MB
Hi Joe,
On Wed, Apr 12, 2017 at 7:46 PM, Joe Watkins wrote:
> This RFC was left open for 5 days past the end of voting as declared on
> the RFC.
>
Thank you, I forgot about this.
IMHO, it's a shame for us we should have inconsistent and insecure function
signature for a new function.
I'm going
On 12/04/2017 17:21, Adam Baratz wrote:
>>
>>> I'd suggest adding a warning to the manual instead.
>>
>> I think that's a requirement in any case.
>
>
> I'd be most comfortable with this approach. I'd worry about adding a
> PDO::PARAM_NUMERIC type without investigating how it needs to function fo
>
> > I'd suggest adding a warning to the manual instead.
>
> I think that's a requirement in any case.
I'd be most comfortable with this approach. I'd worry about adding a
PDO::PARAM_NUMERIC type without investigating how it needs to function for
each DB, which feels like scope creep. If it star
Morning,
This RFC was left open for 5 days past the end of voting as declared on the
RFC.
I have closed the vote, and moved it out of voting section on RFC index.
Cheers
Joe
On Sat, Apr 1, 2017 at 3:50 AM, Yasuo Ohgaki wrote:
> Hi all,
>
> - insecure signature (it ignores strong RFC 5689 re
