Re: [RFC] Return type-hint

On Thu, Jul 29, 2010 at 09:43, Ferenc Kovacs <info@tyrael.hu> wrote: > On Thu, Jul 29, 2010 at 3:49 AM, Felipe Pena <felipensp@gmail.com> wrote: >> Hi all, >> I've updated the patch and the RFC that proposes the return type-hint >> implementation (Engine + Reflection). >> The proposed implementation is working just like the last changes in the >> parameter type-hint (in trunk). i.e. working with the "scalar" and >> "numeric" >> pseudo-types. >> >> http://wiki.php.net/rfc/returntypehint >> >> Thoughts? >> >> -- >> Regards, >> Felipe Pena >> > > > Hi, I would love this feature. > But I have some concerns. > AFAIK you can declare classes with the name int ,scalar, etc. so > hinting anything else than class names can be ambiguous. > Or we have to set these keywords as reserved, so nobody could declare > classes with such names. Weren't they already made reserved with the parameter type hinting patch? > But in this case, this would be a big BC problem, especially, because > I think that there is many project out there which uses type > names(int, object, etc.) as classname. > > Try to search "class Object{" or "class Object extends" on google > codesearch. > > Maybe this was resolved with the last scalar type hinting patch, which > got merged to the trunk, I don't know. > > ps: the spam filter rejected my previous email because of the > codesearch links... > > Tyrael > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Daniel Egeberg