On Thu, Sep 14, 2017 at 4:42 AM, Sara Golemon wrote:
> https://wiki.php.net/rfc/rfc.voting-threshold
>
> This topic has come up on the mailing list a few times, so I'd like to
> formally open the topic for discussion.
>
> I'm generally pretty liberal when it comes to allowing the PHP
> language t
On 14.09.2017 at 00:08m, Zeev Suraski wrote:
> On 14 Sep 2017, at 1:03, Christoph M. Becker
> mailto:cmbecke...@gmx.de>> wrote:
>
> On 13.09.2017 at 23:38, Zeev Suraski wrote:
>
> -Original Message-
> From: Christoph M. Becker [mailto:cmbecke...@gmx.de]
> Sent: Thursday, September 14, 2
On 14 Sep 2017, at 1:03, Christoph M. Becker
mailto:cmbecke...@gmx.de>> wrote:
On 13.09.2017 at 23:38, Zeev Suraski wrote:
-Original Message-
From: Christoph M. Becker [mailto:cmbecke...@gmx.de]
Sent: Thursday, September 14, 2017 12:25 AM
To: Sara Golemon mailto:poll...@php.net>>; PHP i
On 13.09.2017 at 23:38, Zeev Suraski wrote:
>> -Original Message-
>> From: Christoph M. Becker [mailto:cmbecke...@gmx.de]
>> Sent: Thursday, September 14, 2017 12:25 AM
>> To: Sara Golemon ; PHP internals
>> Subject: [PHP-DEV] Re: [RFC][Discuss] Increase non-syntax runtime-impacting
>> RF
> -Original Message-
> From: Christoph M. Becker [mailto:cmbecke...@gmx.de]
> Sent: Thursday, September 14, 2017 12:25 AM
> To: Sara Golemon ; PHP internals
> Subject: [PHP-DEV] Re: [RFC][Discuss] Increase non-syntax runtime-impacting
> RFC votingthreshold to 60%
>
> On 13.09.2017 at 22:4
Hi Jakub,
I already replied to you off-list, but for the benefit of people on-list…
Jakub Zelenka wrote:
On Sun, Sep 10, 2017 at 2:24 AM, Andrea Faulds wrote:
Hi everyone,
Craig Duncan previously sparked discussion here about JSON's
error-handling behaviour. Unfortunately, his attempt to ch
On 13.09.2017 at 22:42, Sara Golemon wrote:
> https://wiki.php.net/rfc/rfc.voting-threshold
>
> This topic has come up on the mailing list a few times, so I'd like to
> formally open the topic for discussion.
>
> I'm generally pretty liberal when it comes to allowing the PHP
> language to evolve
https://wiki.php.net/rfc/rfc.voting-threshold
This topic has come up on the mailing list a few times, so I'd like to
formally open the topic for discussion.
I'm generally pretty liberal when it comes to allowing the PHP
language to evolve and explore its identity, but the truth is a
feature that
On Wed, Sep 13, 2017 at 8:59 AM, Tony Marston wrote:
> "Sara Golemon" wrote in message
> news:CAESVnVpUkM_W9xF+0Qt=2M61dGy40gtOehFo=u_f3gd87rm...@mail.gmail.com...
>> +0.1 to removing case-insensitive constants, though we'd need to
>> define both "null" and "NULL" (similar for true and false) sin
"Ryan Pallas" wrote in message
news:caobuzdtmhxq285hwmc3x9th2rj9d7ty3vnhnpcbzdceppch...@mail.gmail.com...
On Wed, Sep 13, 2017 at 2:59 AM, Tony Marston
wrote:
You seem to forget that autoloading is an option, not a requirement. I
don't use autoloading in my 14 year old framework for seve
"Levi Morrison" wrote in message
news:cafmt4nrc43y-nl_v85qt7jgv1ohm0y4kexhb4e3mi1ejhj0...@mail.gmail.com...
On Wed, Sep 13, 2017 at 2:59 AM, Tony Marston
wrote:
People who think that case sensitive software is cool are deluding
themselves. When I started working on mainframe computers (UNIVA
On Wed, Sep 13, 2017 at 8:06 AM, Rowan Collins
wrote:
> On 13 September 2017 14:15:43 BST, Ryan Pallas
> wrote:
> >I must be missing something, there is no autoloader shipped with PHP.
>
> Just to be pedantically correct, there actually is an implementation
> shipped, see http://php.net/spl_auto
On Wed, Sep 13, 2017 at 2:59 AM, Tony Marston wrote:
> People who think that case sensitive software is cool are deluding
> themselves. When I started working on mainframe computers (UNIVAC and IBM)
> in the early 1970s everything was case-insensitive. This was only changed by
> people who did not
On 13 September 2017 14:15:43 BST, Ryan Pallas wrote:
>I must be missing something, there is no autoloader shipped with PHP.
Just to be pedantically correct, there actually is an implementation shipped,
see http://php.net/spl_autoload It's even the default if you don't pass your
own function to
On 13/09/17 09:59, Tony Marston wrote:
> People who think that case sensitive software is cool are deluding
> themselves. When I started working on mainframe computers (UNIVAC and
> IBM) in the early 1970s everything was case-insensitive.
Life was so much easier when using an RTTY as the keyboard
Regards,
On 12 September 2017 21:35:51 BST, Levi Morrison wrote:
>On Tue, Sep 12, 2017 at 11:59 AM, Rowan Collins
> wrote:
If we want function and class references, they should have their
>own,
unambiguous, syntax.
>>
>> I stand by this assertion. Consider the following statement:
>>
>> $
On Wed, Sep 13, 2017 at 2:59 AM, Tony Marston
wrote:
>
>>
> You seem to forget that autoloading is an option, not a requirement. I
> don't use autoloading in my 14 year old framework for several reasons:
> - An autoloader did not exist when I created my framework.
> - I built an alternative mecha
"Sara Golemon" wrote in message
news:CAESVnVpUkM_W9xF+0Qt=2M61dGy40gtOehFo=u_f3gd87rm...@mail.gmail.com...
On Tue, Sep 12, 2017 at 5:02 AM, Christoph M. Becker
wrote:
Even if these issues could be resolved, I still think allowing both
case-sensitive and case-insensitive constant identifiers
18 matches
Mail list logo
