Thanks Anthony for the thorough explanation and your view on the matter, highly appreciated. I am sure that long-term developers have gone through both ends of the strong types, either loving their lack while picking up php for the first time, either cursing it's lack later on along the way.
As you mentioned you can pretty much do anything in PHP in both small setups or even "enterprise" - god I hate that word - so it would make sense to have something that gives both parties what they want. Having said this, I am truly hoping we can put an end to all this and have your current RFC in and move along. Regards Stelian On Fri, Mar 13, 2015 at 5:10 PM, Johannes Ott <m...@deroetzi.de> wrote: > Thanks for the clear statement, which lights up the fog a little bit for. > > Watching out for a scalar typehints feature for round about 10 years > without knowing about this internal list, I always was wondering what > can be so complicated to implement it, because I already evaluated some > different ways how to do this for my thesis. > > I already thought about a political reason for that. I'm with you that > your Dual RFC is the right solution to satisfy the needs of all of the > three mentioned groups in my opinion as well. > > I would give a clear +1 to it, but I don't have any voting karma yet! > > Regards > -- > DerOetzi > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php >
