Re: [RFC][DISCUSSION] Strict Argument Count

Hi, 2015-03-05 20:08 GMT-03:00 Yasuo Ohgaki <yohgaki@ohgaki.net>: > Hi Marcio, > > On Fri, Mar 6, 2015 at 6:36 AM, Marcio Almada <marcio.web2@gmail.com> > wrote: > >> It would be nothing new or weird. It's just a simple compile time check. >> We already "inspect" code in many other situations while compiling and a >> lot of behaviors during execution already depend on compile time checks. I >> don't think this is "too much". It might sound unusual, at first, but there >> is nothing wrong with this. > > > I really like your idea. You proved usefulness very well by your research.. > My only concern is non-language construct detection by compiler. I'll vote > "yes" regardless of my suggestion if it's not an issue. > Great, thanks. > Zeev suggested better path for migration, not to raise errors > (E_ERROR/E_WARNING/E_NOTICE) instead raise E_DEPRECATED/E_STRICT, for PHP7 > in other thread. You may consider the suggestion while I think E_WARNING is > OK. > > You are right about this. I'll setup a yes/no vote + a vote to decide between E_WARNING (for consistency), E_DEPRECATED or E_STRICT. For me this is just a detail but maybe it's very important to others, so better to let each voter decide upon it. Regards, > > -- > Yasuo Ohgaki > yohgaki@ohgaki.net > > Regards, Márcio