Re: type hinting

On Fri, 2008-01-04 at 18:09 +0100, Pierre wrote: > On Jan 4, 2008 6:01 PM, Sam Barrow <sam@sambarrow.com> wrote: > > > > On Fri, 2008-01-04 at 17:53 +0100, Pierre wrote: > > > On Jan 4, 2008 5:53 PM, Pierre <pierre.php@gmail.com> wrote: > > > > On Jan 4, 2008 4:52 PM, Gregory Beaver <greg@chiaraquartet.net> wrote: > > > > > > > > > But I *don't* want my functions to take an argument of arbitrary type > > > > > - > > > > > it is in fact you who are missing the point. A type hint is a poor > > > > > solution to a real problem that is much more easily solved via simple > > > > > input validation and graceful error handling. The current situation in > > > > > PHP provides a much more flexible solution to the same problem. > > > > > > > > Unlike our OO strictness (E_FATAL!!), nothing will prevent you to use > > > > > > Read: othing will prevent you to >do not< use it :) > > > > > > > So you're saying if you don't like it just don't use it? > > Yes, that's the meaning of "optional" I suppose :) > > My idea about it (I did not test the patch, so correct me if I > misunderstood the proposal) was to leave the default as it is now: > > function($a) > what Greg likes to always use ;) > function(mixed $a) > little syntax sugar, same as the previous one > function(int $a) > etc. > Exactly. I just added the "mixed" type hint which is the same as using no type hint. The new patch is attached. Extra keywords (real, long, double, etc.) have been taken out. The available type hints are now mixed, int, float, bool, string, scalar, num, resource, and object. And of course array and class type hints still work.

Attachment: [text/x-patch] scalartypehinting.patch