> On Sun, Jan 10, 2021, 9:30 AM Reindl Harald (privat)
> wrote:
>
> > what a silly bullshit
> >
> > just because you ar enot capable to setup and properly maintain a
> > webserver it's not "best practice" to outsource it into the cloud and
> > hope everything is magically fine
> >
> > it's likely
On 13/01/2021 12:51, Marco Pivetta wrote:
For me, runtime behavior is:
[...]
* a production outage risk
If your production code can cause outages based on E_DEPRECATED notices,
then that's a bug in your code. I can't think of any justification for a
production system to abort because of
Hey Benjamin
On Wed, Jan 13, 2021 at 1:47 PM Benjamin Eberlei
wrote:
> I get where you are coming from, but side-effect based
> notices/deprecations is just the way PHP works at the moment and as such
> this existing mechanism should be used and extended.
>
> I do have (vague) plans to tackle al
On Wed, Jan 13, 2021 at 1:34 PM Marco Pivetta wrote:
> On Sun, Jan 10, 2021 at 2:48 AM G. P. B. wrote:
>
>> Just to clarify this raises an E_DEPRECATED right?
>> Could it make sense to raise E_USER_DEPRECATED instead?
>>
>
> I hadn't checked this before, but as per George's message, this is
> wo
On Wed, Jan 13, 2021 at 1:05 PM Brent Roose wrote:
> Hi Sara
>
> > On 22 Dec 2020, at 19:54, Sara Golemon wrote:
> >
> > On Tue, Dec 22, 2020 at 12:35 PM Nicolas Grekas <
> > nicolas.grekas+...@gmail.com> wrote:
> >
> >> It would be great to allow adding this attribute on classes. What about
> >
On Sun, Jan 10, 2021 at 2:48 AM G. P. B. wrote:
> Just to clarify this raises an E_DEPRECATED right?
> Could it make sense to raise E_USER_DEPRECATED instead?
>
I hadn't checked this before, but as per George's message, this is worrying.
I've been quite loud about it in the past, but static met
Hi Sara
> On 22 Dec 2020, at 19:54, Sara Golemon wrote:
>
> On Tue, Dec 22, 2020 at 12:35 PM Nicolas Grekas <
> nicolas.grekas+...@gmail.com> wrote:
>
>> It would be great to allow adding this attribute on classes. What about
>> allowing it right now and not bind it to any runtime side-effect?
On 13/01/2021 09:16, Pierre R. wrote:
Instead of trying to restrict types that can be used as keys, may be
this should be the time to have enumerables, lists, maps, vectors,
sets, types, dictionaries, ... in PHP standard library ? A third party
tool such as PHP-DS should be part of core API ins
Hi internals.
I've been coding in PHP for 15 years now, and spend most days using it to
transform content into meaningful data.
Most of this is pulling out prices and attributes of certain products from
HTML, for example, grabbing the price from content such as "Total price
including delivery: £1
On Sun, 10 Jan 2021 at 08:10, Rene Veerman <
rene.veerman.netherla...@gmail.com> wrote:
> i run a website which i want to harden against hacking by 3rd parties.
Hi Rene,
I'm not sure the PHP Internals mailing list is the best place to ask for
this kind of help.
And what you're talking about c
Hi Matthew
On Wed, Jan 13, 2021 at 7:15 AM Matthew Brown wrote:
>
> This proposal is interesting, and I see why the enum proposal makes it
> useful.
>
> Supporting this will mean a small amount of work for me (assuming it
> passes) and other static analysis tools, but I don't want that to factor
Le 13/01/2021 à 10:08, Rowan Tommins a écrit :
On 12/01/2021 16:51, Marco Pivetta wrote:
Whether the problem can be mitigated is what should be discussed, but
the
problem is objectively there.
Hi all,
Like others, I like the *idea* of object keys, but worry about its
practical impact.
A
On 12/01/2021 16:51, Marco Pivetta wrote:
Whether the problem can be mitigated is what should be discussed, but the
problem is objectively there.
Hi all,
Like others, I like the *idea* of object keys, but worry about its
practical impact.
A few scatter-gun thoughts on possible approaches,
13 matches
Mail list logo
