Re: [RFC] Reclassifying engine warnings

From: Date: Wed, 28 Aug 2019 19:30:07 +0000
Subject: Re: [RFC] Reclassifying engine warnings
References: 1 2 3  Groups: php.internals 
Request: Send a blank email to internals+get-106766@lists.php.net to get a copy of this message
Hi! > But @$foo++ is just a really bad way of writing either $foo++ or $foo = 1. If you're working in an environment where you aren't sure if $foo has been mentioned already or not (ideally, you never have to, practically, you sometimes are) it's much easier to just do $foo++ than write code to figure out whether $foo has been already initialized. Note that while a lot of PHP code is written in IDE-assisted unit-tested statically-analyzed CI-gated environments, it's not all PHP code. Sometimes you want to do stuff in quick-n-dirty way, even if it's not exactly production grade, and PHP traditionally has been excellent (probably one of the best languages around) for that. I think we shouldn't abandon that. -- Stas Malyshev smalyshev@gmail.com

« previous php.internals (#106766) next »