Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108241
To: internals@lists.php.net
References: <CAKtGGAsh-38W1UjgDaoQFzhKNOqTy3QGV8fE1-6-PPob2zw6Vw@mail.gmail.com>
 <CAF+90c8yAqHeLRzeX0sYxnQ30JAtg=Ubp7sDyonCkS5V7goN5A@mail.gmail.com>
 <5DC86728-1BBF-4DCA-8A6B-9B0B190DB99D@newclarity.net>
 <CACXBjuhpy3b0fpKHqtDbWDiwVSruRa_NgNUaLOQrduKY-WAx3g@mail.gmail.com>
 <3091DC6D-E03B-4AF5-8DC6-F3B2772956BD@newclarity.net>
 <5d1eaf45-d888-3fe6-7c40-02b0c8c81b61@gmail.com>
 <FC578397-3F03-4E4C-B531-FCFE9CC55447@newclarity.net>
Message-ID: <cf84d92d-8e7a-de26-9d08-7d2ac6f9184b@gmail.com>
Date: Sat, 25 Jan 2020 15:11:36 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <FC578397-3F03-4E4C-B531-FCFE9CC55447@newclarity.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] Typed array properties V2
From: rowan.collins@gmail.com (Rowan Tommins)

On 25/01/2020 00:12, Mike Schinkel wrote:

> So saying "use a static analyzer" is IMO just pointing out an overall 
> weakness that PHP can't automatically do static analysis on its own.

I'd just like to repeat that you and Rasmus are in agreement here. He 
didn't say "PHP doesn't need to change because static analyzers exist", 
he said:

 > it would be amazing to have a static analyzer built into PHP
 > ... but that is a huge task and goes way beyond just this particular 
check.

Choosing whether that analysis runs automatically during server startup, 
or as a separate command-line script, is just one detail among many. It 
probably wouldn't make much difference to the rest of the analysis code, 
and it might even make sense for it to support both modes. For instance, 
it might be optional for command-line scripts, so you could have options 
for "analyse and run", "run only", and "analyse only".


 > One of the main strengths of PHP — and IMO one of the reasons for its 
incredibly marketshare — is the ease with which PHP code can be written, 
tested, and deployed.
 > And that ease translated to ubiquity.
 > Adding a recommended build step to that in order to gain correctness 
weakens that value proposition and threatens future ubiquity as other 
language improve.

Yes, the convenience of having something run automatically is definitely 
worth considering, as long as it doesn't introduce new delays and rules 
that get in people's way.

It partly depends what kind of checks were being done, I guess, and 
therefore how much time it would take to run, and how much of a project 
it would need to analyse at once.

Regards,

-- 
Rowan Tommins (né Collins)
[IMSoP]