On 12/08/2019 14:45, Larry Garfield wrote:
I don't think declaring the package in each file is necessarily bad. Every language I've worked in either has you declare a package explicitly or implies it off of the file system and you don't get any say in the matter. Of the two, I prefer the former.
I concur with this, I would much rather specify a reference to external metadata once-per-file than have it controlled by invisible external state.
If I send an individual file to a co-worker, IMO it should be immediately obvious at the top of that file that it belongs to <x> package and may depend on that package definition to control its behaviour (especially if it gets loaded up with declares or editions).
I'll simply be replacing my ubiquitous strict-types declare with whatever was used to reference this package.
Mark Randall -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
