Am 16.03.2022 um 11:39 schrieb Mark Randall <marand...@php.net>: > On 16/03/2022 09:17, Christian Schneider wrote: >> Maybe we should ask ourselves the question: Why would the entire package be >> blocked? Just because it is too big or maybe there *are* subtleties which >> have not been properly resolved? > > It's politics and the practicalities of getting things done.
A nice description of salami slicing tactics ;-) > An all-or-nothing approach will inevitably end up with nothing, because those > who are opposed on principle need only rally around attacking the weakest > element, without the need to address any of the other parts which might > individually be much stronger. > > That's not to say that the weakest elements shouldn't be debated, they should. > > But we shouldn't sabotage ourselves, and bring about a state of permanent > project paralysis, by mandating that semi-related weaker changes are bundled > with stronger ones and must be voted on as a whole. > > It would just open the door to the constant use of a poison pill argument. The problem is you are saying "the weakest should be debated but not right now, let's move forward anyway" and you are also stipulating that the changes are only semi-related. By doing that you're dismissing Patrick's notion that they are more closely related than you acknowledge because he's saying having inconsistent handling of undefined stuff is also a WTF. And at the same time I really hope once we start discussing undefined array indices you won't bring up consistency with undefined variables (and possibly object properties) as the reason to change it. That would feel weird given that you want to treat them as separate issues right now ;-) - Chris -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
