On Sunday 29 July 2001 19:13, [EMAIL PROTECTED] wrote:
...stuff pointing out how you'd get no warning messages when the evil guy
sets the variables from outside.
You missed my point, which is the good guy would get the warning messages
when he tested the code himself without sending in the
Hi Phil!
On Mon, 30 Jul 2001, Phil Driscoll wrote:
On Sunday 29 July 2001 19:13, [EMAIL PROTECTED] wrote:
...stuff pointing out how you'd get no warning messages when the evil guy
sets the variables from outside.
You missed my point, which is the good guy would get the warning messages
On Monday 30 July 2001 11:13, [EMAIL PROTECTED] wrote:
Hi Phil!
Yes Phil, but does your codes rely on warnings messages alone?
No - my code relies on exceedingly thorough and paranoid validation of input,
carefully constructed program flow, painstaking testing at all stages and no
doubt
On Monday 30 July 2001 11:52, Phil Driscoll wrote:
Some people agree with me, others disgree. As long as you have conrol of
your php.ini file, it isn't a problem :) - although it will (indeed already
does!) tend to discourage me, and probably others, from releasing any of my
code for public
Hi Phil!
On Sat, 28 Jul 2001, Phil Driscoll wrote:
That's not going to find half, or a quarter, or whatever of the problems,
since PHP has tools to cleanly handle undefined variables - namely isset()
and empty(). They, or at least isset(), are quite popular.
I always use something
