On 18 Mar 2015 15:52, "Pavel Kouřil" <pajou...@gmail.com> wrote: > > Hello, > > I made that conclusion because in the first example, the library kinda > forces strict mode rules on the caller, even if he doesn't want to use > strict mode - this makes the interoperability of the two modes > problematic.
This is incorrect, library force itself to use right types, not you. I don't see any problems here. The only thing that for sure lacks in PHP and that would make STH better is callable signature types. > Also, the other possible outcome of the scenario (respecting the mode > of the place where the callback is declared), is IMHO problematic as > well, because it does not respect the strict mode of the place where > it is called, making it inconsistent with how the dual mode RFC works > in general. It doesn't matter where the callback or function was declared, it only matters where it was called. It pretty much is consistent.
