Hi all,
On Sat, Jan 16, 2016 at 10:40 AM, Andrea Faulds wrote:
>
> Thomas Punt wrote:
>>
>> Hi internals!
>>
>> Voting has opened for the inclusion of a digit separator in PHP[1]. Voting
>> ends in
>> one week's time on January 20th.
>>
>> Thanks,
>> Tom
>>
>> [1]: http://wiki.php.net/rfc/number_
فروش ويژه لايسنس اصلي (اورجينال) محصولات اصلي مايکروسافت
تخفيفات ويژه تا پايان دي ماه از 20 تا 50 درصد
ويندوز 10 ، آفيس 2016 ، ويندوز سرور و . . .
شما را به ديدن اين کليپ 80 ثانيه اي در مورد مزاياي نسخه هاي اصلي دعوت مي کنيم
http://www.aparat.com/v/oRL04
اطلاعات بيشتر
http://www.microsoftpersi
On 18/01/16 08:12, Yasuo Ohgaki wrote:
> Large numeric literals are not used often. However if it is used, it's
> frustrating to read. e.g. Code audit/review. Why not make computer
> do the job?
>
> I hope more people change their mind.
Where large numbers are used, adding them as strings using t
On 18 January 2016 at 12:22, Lester Caine wrote:
>
> My main need would be hexadecimal code
> which is not covered, so I still need the alternate hacks anyway.
>
Hex is covered, see the first examples in the "Proposal" section
On 18/01/16 07:19, Michael Wallner wrote:
>> Here's an RFC that would extend the syntax of list() to be more useful
>> > with associative arrays:
>> >
>> > https://wiki.php.net/rfc/list_keys
>> >
>> > Please read it and tell me your thoughts.
> Hi!
>
> I found the idea convincing from the first
On 18/01/16 12:25, Leigh wrote:
> My main need would be hexadecimal code
> which is not covered, so I still need the alternate hacks anyway.
>
> Hex is covered, see the first examples in the "Proposal" section
Sorry getting mixed up ;)
Can't use the 0x in some areas, so one ends up with
Lester Caine wrote on 18/01/2016 12:35:
As someone still using 'extract' in legacy code, I can sort of see the
logistics of this, but why not just extend 'extract' to use the current
object rather than the symbol table. It already has handling for
duplicate keys and to prefix the 'array' name to
On 18 January 2016 at 12:35, Lester Caine wrote:
> > Hi!
> >
> > I found the idea convincing from the first read, but maybe it's just my
> > mind's assumptions about list() that I dislike the resulting syntax,
> > yet, it seems to be the logical choice.
> >
> > So, maybe I'm just trying to say, t
What about using objects with list()?
class Point {
public function __construct($x, $y) {
$this->x = $x;
$this->y = $y;
}
}
$point = new Point(21, 42);
list('x' => $x, 'y' => $y) = $point;
Regards
Thomas
Andrea Faulds wrote on 17.01.2016 03:32:
> Hi everyone,
>
> Here's an RFC that would
> How feasible would it be to add an exception to mixed keys? I'm thinking
> list(7 => $a, $b, $c, $d) to specify an initial offset, similar to how you
> can define an array as [7 => 0, 1, 2, 3]. This obviously goes hand in hand
> with my desire for variable keys :)
I would like it to be like, des
Hey all,
following on from previous discussions[1], I am introducing an RFC for
adding HTTP/2 support to the built-in CLI server:
https://wiki.php.net/rfc/cli_server_http2
Given that the RFC contains two potential solutions for implementing this,
I've decided it is best to open up discussion on
Den 2016-01-18 kl. 13:22, skrev Lester Caine:
On 18/01/16 08:12, Yasuo Ohgaki wrote:
Large numeric literals are not used often. However if it is used, it's
frustrating to read. e.g. Code audit/review. Why not make computer
do the job?
I hope more people change their mind.
Where large numbers a
Results for project PHP master, build date 2016-01-18 06:30:27+02:00
commit: 3a8c4a0
previous commit:7e9a6f7
revision date: 2016-01-18 10:52:48+09:00
environment:Haswell-EP
cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores,
stepping 2, LLC 45 MB
> On 18.01.2016, at 03:03, Yasuo Ohgaki wrote:
>
> Hi openssl module maintainers,
>
> This bug https://bugs.php.net/bug.php?id=68276 is categorized
> as pgsql bug, but it would be more appropriate if categorized as
> openssl bug.
>
> This bug report includes PR https://github.com/php/php-src/pu
Hi Leigh,
Leigh wrote:
The uses for this extended syntax go beyond simply populating object
properties, and shoehorning it into extract would pretty much limit it to
this use-case.
In fact I don't think extract() even works on object properties. list()
works with any "variable" (in the isse
Hi Thomas,
Thomas Bley wrote:
What about using objects with list()?
class Point {
public function __construct($x, $y) {
$this->x = $x;
$this->y = $y;
}
}
$point = new Point(21, 42);
list('x' => $x, 'y' => $y) = $point;
You can't do `$x = $point['x'];`, so `list("x" => $x) = $point;` wo
Hi David,
On Tue, Jan 19, 2016 at 2:31 AM, David Zuelke wrote:
>
> I have customers running into this too. I have not yet had time to pick up
> that patch - AFAICT, it's incomplete (see comments).
>
> We are, in parallel, working on getting a fix into libpq, but that's of
> course just a band-a
On 19.01.2016, at 02:36, Yasuo Ohgaki wrote:
>
> Hi David,
>
> On Tue, Jan 19, 2016 at 2:31 AM, David Zuelke wrote:
>>
>> I have customers running into this too. I have not yet had time to pick up
>> that patch - AFAICT, it's incomplete (see comments).
>>
>> We are, in parallel, working on g
Hi again,
Andrea Faulds wrote:
How feasible would it be to add an exception to mixed keys? I'm thinking
list(7 => $a, $b, $c, $d) to specify an initial offset, similar to how
you
can define an array as [7 => 0, 1, 2, 3]. This obviously goes hand in
hand
with my desire for variable keys :)
Oh,
Hi David,
On Tue, Jan 19, 2016 at 11:13 AM, David Zuelke wrote:
>
>> BTW, should I change the bug report category to openssl?
>
> Yeah it's an ext-openssl "problem" (one could also argue the fault is with
> OpenSSL, but meh).
Thanks. Done.
If you need some help for pgsql, I'll.
Regards,
--
Ya
20 matches
Mail list logo
