I'm pretty sure you've never seen my code, so I am not going to comment
on that.
However, speaking not just for myself, two ternary operations and two
functions calls to just prevent a stoppage code of execution, never mind
input filtering for a second, is not entirely reasonable considering the
vast majority of deployed code. This has traditionally been handled with
deprecation, not by blowing up the runtime. That is why I think it's a
bad idea.
I recognize your opinion; however, that sounded a lot like a personal
attack, for which I have no inclination to listen.
Bitte, reg dich ab.
- M.
On 6/2/2011 11:34 AM, Reindl Harald wrote:
Am 02.06.2011 17:01, schrieb Peter Lind:
On 2 June 2011 16:50, Reindl Harald<h.rei...@thelounge.net> wrote:
Am 02.06.2011 16:24, schrieb Marcel Esser:
I am not convinced that making this an error is a good idea.
If I receive a $_GET/$_POST value that I expect to be a string value, but I
actually received an array, this would
mean I need to now explicitly check for it, since it will stop the runtime
otherwise.
so fix your code jesus christ
How about you take your medication, then chill down, then consider
your messages a couple of times before sending? It would make the
atmosphere quite a bit nicer.
how about people learning basics
instead say "this would mean I need to now explicitly check" somebody
should silent shame why he does not? after that i can guess the rest
of coding quality and this programing-styles are the reason for
so many hours of work if somebody out there comes with his code
to our servers (this does not often happen, but too often)
and the reason for most security problems out there
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
