Hi!
> I agree that at first it will feel a little bit weird, especially
> given that PHP in general lacks syntactic sugar (we still don't have a
> short-hand to initialize stdclass objects). We introduced [] back in
> 5.4, and largely it has made readability FAR better (despite some
> people sayin
Stas,
On Mon, Aug 31, 2015 at 11:46 PM, Stanislav Malyshev
wrote:
> Hi!
>
>> Here it is very obvious that we want to import a variable. Especially, I
>> wonder how
>> $array = array_map(function ($x) use ($y) { return $x + $y; }, $array);
>> is making such simple applications more readable? And
Hi!
> Here it is very obvious that we want to import a variable. Especially, I
> wonder how
> $array = array_map(function ($x) use ($y) { return $x + $y; }, $array);
> is making such simple applications more readable? And especially, what value
> does it add here?
It is making it more readable
> Am 01.09.2015 um 04:55 schrieb Rasmus Lerdorf :
>
>> On Aug 31, 2015, at 18:04, Bob Weinand wrote:
>>
>> From the RFC:
>>> all variables used in the body of the anonymous function will automatically
>>> be bound to the anonymous function closure from the defining scope
>>
>> The implementat
Hi Matt,
My friend made a product called sql_firewall for PostgreSQL.
https://github.com/uptimejp/sql_firewall
http://pgsnaga.blogspot.jp/2015/08/postgresql-sql-firewall.html
It's not directly relevant to your proposal, but this kind of database extension
could be alternative.
PDO has parser fo
> On Aug 31, 2015, at 18:04, Bob Weinand wrote:
>
> From the RFC:
>> all variables used in the body of the anonymous function will automatically
>> be bound to the anonymous function closure from the defining scope
>
> The implementation is not capturing all the variables from the outer scope,
Hi all,
Sorry, I was a bit busy during August.
On Wed, Aug 5, 2015 at 5:37 PM, Yasuo Ohgaki wrote:
> I sent work in progress PR for this and updated the RFC.
>
> https://github.com/php/php-src/pull/1455
> TODO: Add/modify tests. Add 0 mode support for PG(precision). Add
> WDDX/XMLRPC PG(serializ
Hey, thanks for your feedback, but I think you'd got one or two things wrong…
> Am 01.09.2015 um 02:24 schrieb Stanislav Malyshev :
>
> Hi!
>
>> in this RFC. The main addition (which is extended by that btw) is making
>> the syntax shorter. Which, in turn, makes it easier to write and read
>
>
Hi!
> in this RFC. The main addition (which is extended by that btw) is making
> the syntax shorter. Which, in turn, makes it easier to write and read
Shrtr dsnt lwys mks thngs esr 2 rd.
Sometimes it's quite the opposite.
> It would be much easier to read and write with the short syntax:
>
>
Hi,
I\'ve been contributing with RFCs and bug fixes in the past. A VCS account
would be handy for the very obvious fixes.
PS: Bob Weinand pointed me to this form.
Thanks!
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Mon, Aug 31, 2015 at 5:16 PM, Anatol Belski wrote:
> Hi Jakub,
>
>> -Original Message-
>> From: jakub@gmail.com [mailto:jakub@gmail.com] On Behalf Of Jakub
>> Zelenka
>> Sent: Monday, August 31, 2015 10:13 PM
>> To: Anatol Belski
>> Cc: PHP internals list ; Ferenc Kovacs
>> ; P
On Tue, 01 Sep 2015 00:05:35 +0300, Stanislav Malyshev
wrote:
Hi!
I had this RFC in draft since some time, but delayed it due to all
the ongoing PHP 7 discussions. Also we have no master branch to merge
features in until 5.4 EOL. Thus I'm reviving this now.
Time for the first RFC targeting
Hi Jakub,
> -Original Message-
> From: jakub@gmail.com [mailto:jakub@gmail.com] On Behalf Of Jakub
> Zelenka
> Sent: Monday, August 31, 2015 10:13 PM
> To: Anatol Belski
> Cc: PHP internals list ; Ferenc Kovacs
> ; Pierre Joye
> Subject: Re: [PHP-DEV] openssl_seal new param
>
>
Hi!
> I had this RFC in draft since some time, but delayed it due to all
> the ongoing PHP 7 discussions. Also we have no master branch to merge
> features in until 5.4 EOL. Thus I'm reviving this now.
>
> Time for the first RFC targeting PHP 7.1 (assuming PHP 8 isn't going
> to be the next versi
Hello,
I've written up an RFC for supporting generic classes and methods in
PHP, and I'd love to hear your thoughts about it.
https://wiki.php.net/rfc/generics
Cheers,
--
Ben Scholzen 'DASPRiD'
Community Review Team Member | m...@dasprids.de
Zend Framework | http://www.dasprids.
Hi Anatol,
On Mon, Aug 31, 2015 at 12:17 PM, Anatol Belski
wrote:
>
> > Hi,
> >
> > I have been looking to https://bugs.php.net/bug.php?id=60632 which is
> about
> > failing (segfaulting) openssl_seal when used with cipher alg that
> requires IV (e.g.
> > AES-128-CBC). I think that the patch look
I had this RFC in draft since some time, but delayed it due to all the ongoing
PHP 7 discussions. Also we have no master branch to merge features in until 5.4
EOL. Thus I'm reviving this now.
Time for the first RFC targeting PHP 7.1 (assuming PHP 8 isn't going to be the
next version ;-)):
The
Den 2015-08-26 kl. 13:19, skrev Niklas Keller:
Hi Björn,
Ah yes, then a set_throwable_handler would be needed. A final question:
Would it
be an alternative to update set_error_handler to also handle
\Throwable\Error\*
exceptions and let set_exception_handler catching same type of exceptions
Hi Jakub,
> -Original Message-
> From: jakub@gmail.com [mailto:jakub@gmail.com] On Behalf Of Jakub
> Zelenka
> Sent: Sunday, August 30, 2015 9:11 PM
> To: PHP internals list ; Ferenc Kovacs
> ; Anatol Belski ; Pierre Joye
>
> Subject: [PHP-DEV] openssl_seal new param
>
> Hi,
>
>
Results for project php-src-nightly, build date 2015-08-31 05:00:00+03:00
commit: 54a831829ad18144caec1afbec7ff4a65bc79a5d
revision_date: 2015-08-30 20:25:10+02:00
environment:Haswell-EP
cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores, stepping
2, LLC 45 MB
20 matches
Mail list logo
