Le 11/02/2016 07:27, Stanislav Malyshev a écrit :
Hi!
I just added support for '[]' on strings and '{}' to the PR.
Examples :
$string[] = 'a'; // equivalent to : $string[strlen($string)]
$string{} = 'a'; // For consistency
That's probably not a good idea, and certainly is not good for the
On Wed, Feb 10, 2016 at 6:19 PM, Andrea Faulds wrote:
> Why isn't "Sofie Vanderplaetsen" banned from the list yet? It's repeated
> spam.
>
Because there's no response team?
*hides*
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi!
> RFC must maintain consistency across existing features/specifications,
There's a lot of things people call "consistency", apparently. I don't
see inventing new syntax for doing concatenation to have anything to do
with consistency.
> make things worse certainly. Making patch and/or RFC sim
Hi Stas,
On Thu, Feb 11, 2016 at 3:27 PM, Stanislav Malyshev wrote:
>
>> I just added support for '[]' on strings and '{}' to the PR.
>>
>> Examples :
>>
>> $string[] = 'a'; // equivalent to : $string[strlen($string)]
>>
>> $string{} = 'a'; // For consistency
>
> That's probably not a good idea,
Hi!
> I just added support for '[]' on strings and '{}' to the PR.
>
> Examples :
>
> $string[] = 'a'; // equivalent to : $string[strlen($string)]
>
> $string{} = 'a'; // For consistency
That's probably not a good idea, and certainly is not good for the RFC -
the patch now does two unrelated t
Hi,
Why isn't "Sofie Vanderplaetsen" banned from the list yet? It's repeated
spam.
--
Andrea Faulds
https://ajf.me/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi!
On 9 February 2016 at 13:56, Matt Prelude wrote:
> I feel that the CoC has a much greater chance of achieving consensus if we
> don't
> try to impose a 'court of law' alongside it, especially considering that
> most
> proposals for a 'court' have been secretive and focused on privacy rather
>
Thanks so much for taking this up Derick! :)
The mission points could be reworked a bit.
> * Make everybody happier, especially those responsible for developing PHP
> itself.
This has a slight insinuation that non-internals/new people are
annoying to the core PHP team. Also, what makes one happ
>
> I think the best way would be to try and provide tests (part of the PR)
> and test environment for this change.
>
> If the latter can't be provided, maybe instructions how to create one (as
> you guys probably have far more experience then us).
I'll certainly provide tests. Maybe this vagrant
On 10 February 2016 at 14:34, François Laupretre wrote:
> Hi,
>
> I just added support for '[]' on strings and '{}' to the PR.
>
> Examples :
>
> $string[] = 'a'; // equivalent to : $string[strlen($string)]
>
> $string{} = 'a'; // For consistency
Unless I'm missing some subtleties, that appears t
Le 10/02/2016 15:34, Dan Ackroyd a écrit :
On 10 February 2016 at 07:00, Yasuo Ohgaki wrote:
Additional comment on this
php > $v=array(1,2,3);
php > $v .= 'abc';
I think $v .= 'abc' should not destroy array variable. It's minor issue, though.
That is the current behaviour. Trying to slip "b
On 10 February 2016 at 07:00, Yasuo Ohgaki wrote:
> Additional comment on this
>
> php > $v=array(1,2,3);
> php > $v .= 'abc';
>
> I think $v .= 'abc' should not destroy array variable. It's minor issue,
> though.
That is the current behaviour. Trying to slip "bug fixes" into RFCs is
a very bad
Hi,
I just added support for '[]' on strings and '{}' to the PR.
Examples :
$string[] = 'a'; // equivalent to : $string[strlen($string)]
$string{} = 'a'; // For consistency
With this change, AFAIK, '{}' and '[]' notations are handled exactly the
same way (the only difference was that the con
Results for project PHP master, build date 2016-02-10 06:28:00+02:00
commit: 1c3edc3
previous commit:4fcc3f7
revision date: 2016-02-09 23:37:11+08:00
environment:Haswell-EP
cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores,
stepping 2, LLC 45 MB
14 matches
Mail list logo
