On Jan 4, 2008 6:01 PM, Sam Barrow <[EMAIL PROTECTED]> wrote: > > On Fri, 2008-01-04 at 17:53 +0100, Pierre wrote: > > On Jan 4, 2008 5:53 PM, Pierre <[EMAIL PROTECTED]> wrote: > > > On Jan 4, 2008 4:52 PM, Gregory Beaver <[EMAIL PROTECTED]> 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. -- Pierre http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
