Hi Andrey,
1. The wording here implies that these are the *only* attributes
allowed. In the interest of forward-compatibility, I'd allow arbitrary
attributes as well.
I just try to implement something like this, to allow arbitrary
attributes. Is this what you prefer?
http_cookie_set('foobar
On 24 July 2017 at 22:55, li...@rhsoft.net wrote:
> what is that for nosense?
>
> "550-Spammy URLs in your message" is for sure *not* a response from our
> mailserver sicne i am the guy who implemented the spamfilter and knows
> every single possible reject message
>
That message looks like it w
On 20/7/17 10:31 am, Anatol Belski wrote:
Hi Chris,
-Original Message-
From: Christopher Jones [mailto:christopher.jo...@oracle.com]
Sent: Thursday, July 20, 2017 2:11 AM
To: Anatol Belski ; php-...@lists.php.net; Tianfang Yang
Subject: Re: [PHP-CVS] com php-src: fix default args for
Results for project PHP master, build date 2017-07-23 19:22:19-07:00
commit: 445e13b
previous commit:a6b529c
revision date: 2017-07-23 23:17:12+02:00
environment:Haswell-EP
cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores,
stepping 2, LLC 45 MB
what is that for nosense?
"550-Spammy URLs in your message" is for sure *not* a response from our
mailserver sicne i am the guy who implemented the spamfilter and knows
every single possible reject message
Weitergeleitete Nachricht
Betreff: ezmlm warning
Datum: 24 Jul 2017 2
Hi Johannes
2017-07-24 20:10 GMT+02:00 Johannes Schlüter :
> With this very specific item we need to make sure the server actually
> has pdo_mysql enabled. I currently have no access and assume it does.
The bug tracker provides an "admin" interface which have a phpinfo()
page[1], and yes bugs.php
On Mo, 2017-07-24 at 11:51 +0200, Niklas Keller wrote:
> It's unmaintained code, nobody wants to touch it. Any attempt to
> improve anything doesn't go anywhere, because there are too many
> people saying the current state is fine.
>
> See https://github.com/php/web-bugs/pull/26 for an example.
F
Hi Niklas
2017-07-24 11:51 GMT+02:00 Niklas Keller :
> It's unmaintained code, nobody wants to touch it. Any attempt to improve
> anything doesn't go anywhere, because there are too many people saying the
> current state is fine.
I doubt the fact that because its written this way is making no one
>
> Dear internals,
>
> Don't you think allowing to throw an exception as the right side of null
> coalescing operator would be a good idea?
>
> Something like:
>
> echo $a ?? throw new \RuntimeException('foo');
>
> Regards,
> Tim
>
Sometimes that would be really helpful. What you can do is someth
2017-07-24 10:15 GMT+02:00 Kalle Sommer Nielsen :
> Hi Johannes
>
> 2017-07-24 0:03 GMT+02:00 Johannes Schlüter
> > It is also good for the PHP ecosystem at large to show we're using
> > libraries, where it makes sense. If we use a variety we're also not
> > favoring single ones :)
>
> As much as
LS,
Because of the valid arguments to set(raw)cookie and
session_set_cookie_params to become lengthly functions, I reconsidered
the proposal. It now consists of two possibilities. One is add samesite
as argument and second one is to have these functions accept an array of
options. One can rea
Thanks all for the comments.
While I understand the motivations & reasons I think I would prefer not to
help in this specific case.
Nothing wrong with the approach but different then what I was expecting to
spend my free time on.
I hope everything goes ok.
Count on me for further improvements if
Hi Johannes
2017-07-24 0:03 GMT+02:00 Johannes Schlüter
> It is also good for the PHP ecosystem at large to show we're using
> libraries, where it makes sense. If we use a variety we're also not
> favoring single ones :)
As much as I agree with that, I do not see a big thing that using a
library
Hello Andreas,
On Sun, Jul 23, 2017 at 9:26 PM, Andreas Treichel wrote:
> Hello Andrey,
>
>> That's what I was afraid of, and what I suggested be changed.
>>
>> If we had a similar, array-of-attributes API that did NOT ignore or
>> trigger warnings for unknown attributes, everybody using PHP woul
Dear internals,
Don't you think allowing to throw an exception as the right side of null
coalescing operator would be a good idea?
Something like:
echo $a ?? throw new \RuntimeException('foo');
Regards,
Tim
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://w
15 matches
Mail list logo
