On Wed, Aug 28, 2019 at 4:33 AM Nikita Popov wrote:
> I think it's time to take a look at our existing warnings & notices in the
> engine, and think about whether their current classification is still
> appropriate. Error conditions like "undefined variable" only generating a
> notice is really
Hi,
The PHP development team announces the immediate availability of PHP
7.2.22. This is a security release which also contains several minor bug
fixes.
All PHP 7.2 users are encouraged to upgrade to this version.
For source downloads of PHP 7.2.22 please visit our downloads page.
Windows
Hi!
>> encountered a PHP developer who thought using uninitialized variables
>> was fine.
>
> Now you have. Nice to meet you.
And there are more of us. You learn something new every day!
>> I knew it worked, but I always considered this to basically be
>> the PHP equivalent of undefined
Am 29.08.2019 um 18:25 schrieb Aegir Leet :
> Before reading the responses to this thread, I had honestly never
> encountered a PHP developer who thought using uninitialized variables
> was fine.
Now you have. Nice to meet you.
> I knew it worked, but I always considered this to basically be
>
> Le 29 août 2019 à 18:25, Aegir Leet a écrit :
>
> Either way, if you want a less strict language, that language already
> exists: It's the current version of PHP and you and everyone else who
> likes the way it works can keep using it.
> Meanwhile, I think most people currently doing serious
> Le 29 août 2019 à 18:13, Matthew Brown a écrit :
>
> I don’t think it’s helpful to compare C#’s BC policies to PHP’s. C# is used
> today mostly as its architect intended at its founding. PHP, having
> transitioned from a templating system to a fully-fledged language, is used
> quite
> From: Aegir Leet
> Either way, if you want a less strict language, that language already
> exists: It's the current version of PHP and you and everyone else who
> likes the way it works can keep using it.
For approximately 3 years. Please remember "end of life". We'd still be using
php5
Before reading the responses to this thread, I had honestly never
encountered a PHP developer who thought using uninitialized variables
was fine. I knew it worked, but I always considered this to basically be
the PHP equivalent of undefined behavior in C. And I don't think anyone
would get mad if
I don’t think it’s helpful to compare C#’s BC policies to PHP’s. C# is used
today mostly as its architect intended at its founding. PHP, having
transitioned from a templating system to a fully-fledged language, is used
quite differently.
> On Aug 29, 2019, at 11:50 AM, Chase Peeler wrote:
>
On Thu, Aug 29, 2019 at 10:22 AM Zeev Suraski wrote:
> On Thu, Aug 29, 2019 at 4:02 PM Aegir Leet via internals <
> internals@lists.php.net> wrote:
>
> > I know what the manual says about notices. But I don't agree with
> > interpreting "could happen in the normal course of running a script" as
On Thu, Aug 29, 2019 at 3:48 PM Alexandru Pătrănescu
wrote:
> Zeev, you might not agree with rules and hints but I strongly believe that
> they are great rules.
>
I think many of them are great (such as not posting when agitated, thinking
about what you want to say, being respectful, etc.), and
On Thu, Aug 29, 2019 at 4:02 PM Aegir Leet via internals <
internals@lists.php.net> wrote:
> I know what the manual says about notices. But I don't agree with
> interpreting "could happen in the normal course of running a script" as
> "it's perfectly fine if this part of your code triggers a
I know what the manual says about notices. But I don't agree with interpreting
"could happen in the normal course of running a script" as "it's perfectly fine
if this part of your code triggers a notice consistently and every time it goes
down this particular code path". Rather, I've always
Hi,
True! Thanks for bringing this up, Nikita.
I wanted to mention the rules on the "Reclassifying engine warnings" thread
as well.
Zeev, you might not agree with rules and hints but I strongly believe that
they are great rules.
Not posting too many times, not posting when you are agitated and
> Le 29 août 2019 à 13:33, Aegir Leet via internals a
> écrit :
>
> I'm sorry, but if you seriously believe doing something that generates a
> notice (or warning, or error, ...) is not a bug - you're delusional.
No, what you think is not at all how notices were designed. From the manual
The PHP development team announces the immediate availability of PHP
7.3.9. This is a security release which also contains several bug fixes.
All PHP 7.3 users are encouraged to upgrade to this version.
For source downloads of PHP 7.3.9 please visit our downloads page.
Windows binaries can be
I'm sorry, but if you seriously believe doing something that generates a
notice (or warning, or error, ...) is not a bug - you're delusional.
That is the very definition of a bug and notices/warnings/errors etc.
are the mechanism the language uses to report these bugs to the
developer. If
On Thu, Aug 29, 2019 at 10:43 AM Nikita Popov wrote:
> Hi internals,
>
> A gentle reminder to everyone that this mailing list has rules, documented
> at https://github.com/php/php-src/blob/master/docs/mailinglist-rules.md.
> In
> particular:
>
And a gentle reminder that these are guidelines
On Thu, 29 Aug 2019 at 08:28, Christian Schneider
wrote:
> Side-note: Which brings us back to the discussion about the downsides of
> language modes but as similar topics keep on popping up (although by the
> same people) you are slowly convincing me that going down that road is the
> best
Hi internals,
A gentle reminder to everyone that this mailing list has rules, documented
at https://github.com/php/php-src/blob/master/docs/mailinglist-rules.md. In
particular:
> 1. If you notice that your posting ratio is much higher than that of
other people, double check the above rules. Try
Am 29.08.2019 um 08:22 schrieb Alexandru Pătrănescu :
> When you write code, in a "productive" way that you mention, it's perfectly
> fine if you write it for you and for now.
>
> But most often, we write code for the future generations of developers that
> could be less skilled, for the future
Zeev,
When you write code, in a "productive" way that you mention, it's perfectly
fine if you write it for you and for now.
But most often, we write code for the future generations of developers that
could be less skilled, for the future you that might have less context.
Also, code will evolve
22 matches
Mail list logo
