Hi!
> It seems to me that this would miss the point, namely to introduce some
> consistency, and to be able to
If working code would be broken, nobody needs "consistency". I've built
tons of software, and never ever any single client asked me "but do you
have 'constistency'? Surely, I'm not again
On 14.09.2017 at 23:22, Stanislav Malyshev wrote:
> [Nikita wrote]
>
>> +1 on doing this. I can understand having case-insensitive constants, but
>> having both case-sensitive and case-insensitive at the same time is weird
>> and rather useless. I imagine the only reason why this "feature" exists
Hi!
> I would also explicitly note that the voting threshold applies to the
> primary RFC vote only, while secondary votes are simple majority votes.
This sounds like a good compromise.
--
Stas Malyshev
smalys...@gmail.com
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe
Hi!
> +1 on doing this. I can understand having case-insensitive constants, but
> having both case-sensitive and case-insensitive at the same time is weird
> and rather useless. I imagine the only reason why this "feature" exists in
> the first place is to support arbitrary casing for true/false/n
On Fri, Sep 15, 2017 at 6:06 AM, Yasuo Ohgaki wrote:
> On Wed, Sep 13, 2017 at 3:24 PM, Joe Watkins
> wrote:
>
>> This proposal was rejected.
>>
>> 6 months has not passed since it was rejected.
>>
>> There will be no vote on these proposals in the near future.
>>
>> Please stop.
>>
>> Joe
>>
>
On Wed, Sep 13, 2017 at 3:24 PM, Joe Watkins wrote:
> This proposal was rejected.
>
> 6 months has not passed since it was rejected.
>
> There will be no vote on these proposals in the near future.
>
> Please stop.
>
> Joe
>
Joe, you have great responsibility as RM for ridiculous hash_hkdf() API
On Thu, Sep 14, 2017 at 12:02 PM, Levi Morrison wrote:
> On Thu, Sep 14, 2017 at 9:38 AM, Sara Golemon wrote:
>> On Tue, Sep 12, 2017 at 8:02 AM, Christoph M. Becker
>> wrote:
>>> Usually constant identifiers are treated case-sensitive in PHP. This is
>>> always the case for constants defined
Hi,
PHP 7.0.24 RC1 was just released and can be downloaded from:
https://downloads.php.net/~ab/
The Windows binaries are available at
http://windows.php.net/qa/
This release contains a number of bugfixes.
For the list of bugfixes that you can target in your testing, please refer to
th
On 14.09.2017 at 17:37, François Laupretre wrote:
> Le 14/09/2017 à 15:38, Alain Williams a écrit :
>
>> I vote for making it case sensitive: simpler for the parser; the
>> programmer
>> rapidly learns that it should be 'TRUE' and not 'true' -- job done.
>
> No need to force people to switch thei
The second release candidate for 7.2.0 was just released and can be
downloaded from:
https://downloads.php.net/~pollita/
Or using the git tag: php-7.2.0RC2
The Windows binaries are available at: http://windows.php.net/qa/
Please test it carefully, and report any bugs in the bug system.
The next r
On Thu, Sep 14, 2017 at 9:38 AM, Sara Golemon wrote:
> On Tue, Sep 12, 2017 at 8:02 AM, Christoph M. Becker
> wrote:
>> Usually constant identifiers are treated case-sensitive in PHP. This is
>> always the case for constants defined via a `const` declaration.
>> However, define() allows to pass
On Thu, Sep 14, 2017 at 11:37 AM, François Laupretre
wrote:
> Le 14/09/2017 à 15:38, Alain Williams a écrit :
>>
>> I vote for making it case sensitive: simpler for the parser; the
>> programmer
>> rapidly learns that it should be 'TRUE' and not 'true' -- job done.
>
>
> No need to force people to
On Tue, Sep 12, 2017 at 8:02 AM, Christoph M. Becker wrote:
> Usually constant identifiers are treated case-sensitive in PHP. This is
> always the case for constants defined via a `const` declaration.
> However, define() allows to pass TRUE as third argument to define a
> case-insensitive constan
Le 14/09/2017 à 15:38, Alain Williams a écrit :
I vote for making it case sensitive: simpler for the parser; the
programmer
rapidly learns that it should be 'TRUE' and not 'true' -- job done.
No need to force people to switch their code to 'TRUE'. Just supporting
case-sensitive 'TRUE', 'true'
On Thu, 14 Sep 2017, at 02:48 PM, Tony Marston wrote:
> Because the English-speaking world invented both computers and the
> languages used to program them.
It was a German that invented binary, so my suggestion is to devolve all
future decisions to the Germans.
On Thu, 14 Sep 2017, at 02:36 PM,
On Thu, Sep 14, 2017 at 02:48:06PM +0100, Tony Marston wrote:
> "Rowan Collins" wrote in message
> news:7394e3ce-b05a-474e-8ab5-a651fdd35...@gmail.com...
> >
> >On 14 September 2017 13:59:20 BST, Tony Marston
> > wrote:
> >>Why should the
> >>English-speaking world be forced to suffer just because
On Tue, Sep 12, 2017 at 8:02 PM, Christoph M. Becker
wrote:
> Hi everybody!
>
> Usually constant identifiers are treated case-sensitive in PHP. This is
> always the case for constants defined via a `const` declaration.
> However, define() allows to pass TRUE as third argument to define a
> case-
"Rowan Collins" wrote in message
news:7394e3ce-b05a-474e-8ab5-a651fdd35...@gmail.com...
On 14 September 2017 13:59:20 BST, Tony Marston
wrote:
Why should the
English-speaking world be forced to suffer just because some minor
languages
cannot handle case folding?
Have you any idea how arrog
On Thu, Sep 14, 2017 at 02:36:27PM +0100, Tony Marston wrote:
> ""Christoph M. Becker"" wrote in message
> news:98ab178e-b999-7e36-5ff5-7b8c28fe0...@gmx.de...
> >
> >On 14.09.2017 at 14:59, Tony Marston wrote:
> >
> >>Introducing case sensitivity into what is mostly a case-insensitive
> >>world ju
On Thu, Sep 14, 2017 at 02:16:47PM +0100, Tony Marston wrote:
> A minor detail. Windows followed all the previous OSes which I had
> used in being case insensitive, which makes unix the odd one out.
> Besides there are far more computers running Windows than unix, so
> unixx should not be used as
""Christoph M. Becker"" wrote in message
news:98ab178e-b999-7e36-5ff5-7b8c28fe0...@gmx.de...
On 14.09.2017 at 14:59, Tony Marston wrote:
Introducing case sensitivity into what is mostly a case-insensitive
world just for the convenience of a few programmers I do not consider to
be acceptable.
On 14/09/17 14:10, Michael Morris wrote:
> On Thu, Sep 14, 2017 at 8:33 AM, Lester Caine wrote:
>
>> UTF8 introduces a level of complexity and can be used used in many
>> places in PHP, but it does seem that there is no drive these days to
>> make the core a clean UTF8 environment. This should pe
On 14 September 2017 13:59:20 BST, Tony Marston wrote:
> Why should the
>English-speaking world be forced to suffer just because some minor
>languages
>cannot handle case folding?
Have you any idea how arrogant this sounds? Why should "the English-speaking
world" get to make up the rules? What
On 14.09.2017 at 14:59, Tony Marston wrote:
> Introducing case sensitivity into what is mostly a case-insensitive
> world just for the convenience of a few programmers I do not consider to
> be acceptable. It would cause more problems for far more people than the
> insignificant few who insist on
Whoops, just noticed I sent this to Zeev directly last night rather than
the list.
-- Forwarded message --
From: Sara Golemon
Date: Wed, Sep 13, 2017 at 10:28 PM
Subject: Re: [PHP-DEV] [RFC][Discuss] Increase non-syntax runtime-impacting
RFC voting threshold to 60%
To: Zeev Surask
"Lester Caine" wrote in message
news:20b8b6fa-ec81-eba9-d33b-b54b815e9...@lsces.co.uk...
On 14/09/17 10:20, Tony Marston wrote:
Then unix came along and FUBAR'd everything. Any advantages of case
sensitive systems are ALWAYS outweighed by their disadvantages.
Unix predates Windows ...
A mi
On Thu, Sep 14, 2017 at 8:33 AM, Lester Caine wrote:
> UTF8 introduces a level of complexity and can be used used in many
> places in PHP, but it does seem that there is no drive these days to
> make the core a clean UTF8 environment. This should perhaps be addressed
> again for PHP8?
>
>
*Cough*
"Daniel Morris" wrote in message
news:1505382004.4078127.1105791680.3a06c...@webmail.messagingengine.com...
On Thu, 14 Sep 2017, at 10:20 AM, Tony Marston wrote:
If the first programming languages in the first computers were case
insensitive, then that should be the standard. Those who introdu
On 14/09/17 10:20, Tony Marston wrote:
> Then unix came along and FUBAR'd everything. Any advantages of case
> sensitive systems are ALWAYS outweighed by their disadvantages.
Unix predates Windows ... the use of such breaks as having spaces in
file names came from that development in addition to t
Le 13/09/2017 à 22:42, Sara Golemon a écrit :
> 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 evolv
On 14 September 2017 10:23:48 BST, Tony Marston
>Would this problem disappear by using UTF8 instead of the Turkish
>character
>set? If so then ten no other solution would be required.
No, the problem has nothing to do with character sets, but with the actual
alphabet that humans in Turkey use, w
On Thu, 14 Sep 2017, at 10:20 AM, Tony Marston wrote:
> If the first programming languages in the first computers were case
> insensitive, then that should be the standard. Those who introduced case
> sensitive languages at a later date should be forced to justify that
> decision.
If the first
""Tony Marston"" wrote in message news:09.43.19300.8e659...@pb1.pair.com...
"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 co
"Sara Golemon" wrote in message
news:CAESVnVp6OKB64WuO9iKEP=l9-qrrfjs+kcoekykulruff-r...@mail.gmail.com...
On Wed, Sep 13, 2017 at 8:59 AM, Tony Marston
wrote:
People who think that case sensitive software is cool are deluding
themselves. When I started working on mainframe computers (UNIV
34 matches
Mail list logo
