Re: Naming of 'weak' type hints

On Mon, Mar 30, 2015 at 4:16 PM, Zeev Suraski <zeev@zend.com> wrote: > All, > > > > One thing that I think we should change is how we refer to the ‘weak’ type > hints. The word ‘weak’ has a negative ring to it, and considering this is > how the language behaves across the board it’s a pretty bad name for this > feature. > > > > Personally I think we should go for ‘dynamic’ when we document it, as this > is the common way to refer to this behavior (dynamic languages). We could > also consider going for ‘lax’ or ‘lenient’ as the opposite of ‘strict’, > although I think we can easily do without introducing a new word into the > vocabulary here. > > > > Thoughts? > > > > Zeev Hello, I would definitely stick with "weak"; it is common naming used across many languages and textbooks. Also, why is the strongly typed mode named "strict" anyways? If anything should change, it should be strict to strong, so PHP doesn't look like a special snowflake. Regards Pavel Kouril