On Wed, 11 Oct 2006, Pierre wrote: > On 10/11/06, Derick Rethans <[EMAIL PROTECTED]> wrote: > > On Wed, 11 Oct 2006, Pierre wrote: > > > > > Doing so you can distinguish invalid values from non existent values. > > > Boolean values are the only case where it is not possible to > > > distinguish FALSE from invalid as they can be FALSE, but it is really > > > not an issue. > > > > If it wasn't an issue I wouldn't have fixed it. > > Ok, I have no time to argue again with you about that. I will revert > it tonight so we will be ready for 5.2.0RC6.
You will do no such thing. I am getting tired of your "but we agreed on this", while that is just in your mind. I didn't agree in the first place that you're changing the API since the original design so I feel free to revert every non-discussed change that you made in the first place. This is one of those issues. And you're also wrong to say that we need this "false if it is invalid data" as you don't need that "null value to see if the var actually exists", as you have filter_has_var() to check this already. You use that function to see if a var exists and check for NULL if the logical filter discarded as wrong data. Then you don't have to do strange tricks to see if you used a boolean filter that returns "false" or "false" because a filter discarded the data. regards, Derick -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
