> -----Original Message----- > From: Rick WIdmer [mailto:vch...@developersdesk.com] > > On 2/28/2012 2:58 PM, Kris Craig wrote: > > > strong int $a = "1"; // Converts to 1. May or may not throw an error > > (I'm still on the fence). > > [If] this is an error, it is no longer PHP.
Rick, I know what you are getting at, and I even agree that this won't work, but please let's avoid extreme aggressive statements. This shuts down the discussion and just makes people angry at you. "This is no longer PHP" is an aggressive complaint that doesn't help anyone understand why this construct is a problem. Instead, please articulate the core problem with the proposal. In this case a better response would be something like: "This re-opens the viral poisoning problem with strict typing that's already been discussed. We can't do this unless you can solve that problem.". Thanks, John Crenshaw Priacta, Inc. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
