Re: hasType() for internal function parameters?

Hi! > Is it a BC break against real code though? Fixing tests isn't a > big deal. What kind of real code would break by turning calls with > the wrong number of args from an error to a warning? Well, if we move to checking in ZPP only, then some of the errors that previously were fatals (like iterator_array("")) would now become warnings. In fact, even type mismatch is a warning for ZPP, which may be unexpected, as it was a fatal before, so we may want to change that. But in some situation, like argument number mismatch, we will have a warning, where before it was a fatal error. Which isn't strictly BC break but allows some code to pass which previously didn't and may hide some bugs. So we may want to be careful there. -- Stas Malyshev smalyshev@gmail.com