Bleh well that's just semantics. Strict typing / type hinting is what I'm talking about; not specifically advocating one or the other.
And yeah this started as an enum proposal, but it came back to this issue. I offered to move this to a separate topic but everyone seems content to just keep talking about it here. I honestly don't care either way. So long as this important discussion isn't just "tabled" yet again I'm good. --Kris 2012/2/26 Ángel González <keis...@gmail.com> > On 26/02/12 05:11, Arvids Godjuks wrote: > > Kris Craig > > > > I usually just read the list, sometimes add if I have something to say > and > > I had voiced my opinion on typehinting before. And you know, just from > the > > stand of a userland developer who has 7-8 years of experience and > devoting > > myself to the excelence at PHP, i see this discussion about adding strict > > typehinting to PHP as ridicilous. I cannot express my thrustration, > because > > i would probably be kicked out of the list permanently. > > The problem is that those, who are actually advocating for this, come > from > > all sorts of languages (or have moved to them some time ago) and now what > > to "make php better". Sorry folks, but I have picked up a script language > > not because it has strict type hinting, but actually because it does not > > have it. And because in web we are working with text. Almost any data we > > get is text and in critical places we just check that data we have is > > actually a number and not a random string. Or is an object of certain > type. > > Or is an array. Or a valid string. And we let the PHP to handle routine > > conversions. And it's good because there can be tons of them per single > > script call. String to number and vice-verse conversions are all over the > > place in almost any script. They are so common, that if you would add > > strict typehinting - you would probably need a type conversion on every > > function/method call. > I'm not so sure about that. In a well-written web application, you would > typically convert them on the first layer, when receiving from the web. > On next usages, your int variables are usually ints already. > > Anyway, you seem to think that people is advocating to add strict typing > to the language, while I haven't seen that in this thread. Only to add type > hinting (and this all began with an enum proposal!), which could be either > strict or weak. > Some people positioned against typehints, have been much more vocal > against strict, of course, as that has much more ground. > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
