Error reporting???

timstring

As far as I can tell, I have every instance on error reporting commented out in php.ini. I am not calling any error reporting commands from inside my scripts. However, I'm still getting "Undefined variable" errors. Where would I look in the INI file to turn the @#as;123 things off?

laserlight

During development, the solution is to fix the error, not ignore it. That is, why is the variable undefined? Maybe you are trying to access an element of the $GET or $POST superglobal arrays, and so you should check with [man]isset[/man] or [man]empty[/man] before accessing them.

In production, the solution is to set display_errors to off, and log errors instead. Error reporting should be kept at a reasonably high level.

timstring

I'm only $_POSTing two variables, and they are valid. The errors I'm getting are for variables in the middle of the script which are nothing more than counters. I had previously deleted a couple of variables that were unused, but shouldn't have been flagged.

traq

So wrap those counters in a conditional statement (so they aren't used unless needed), or give them an initial value ([man]null[/man] would make sense).

timstring

If I were programming an application for a space probe in Fortran, I'd care very much about undefined variables. Voyager I was lost because someone didn't define a variable that should have been a decimal, but Fortran assumed, as it is set up to do, that the variable was an integer. A few decimal points at the distance of millions of miles can really ruin your day.

However, my script is not a life-or-death program needed by rocket scientists. I just want the error reporting gone.

Weedpacket

Because it's so difficult to give a variable a value if it doesn't already have one....

PS: Voyager 1 hasn't been lost. Mariner 1 was aborted when the fact it was processing raw rate data instead of signal-averaged rate data sent it wonky during takeoff. The FORTRAN bug came up during the Mercury program, and involved a [font=monospace].[/font] being substituted for a [font=monospace],[/font].

bradgrafelman

timstring;11039811 wrote:
However, my script is not a life-or-death program needed by rocket scientists.

It's also not for anyone else who wants a script that was written without errors.

timstring

From the days of BASIC, variables that don't have values are considered NULL. There is no reason for these errors to be reported.

Weedpacket

Edsger W. Dijkstra wrote:
It is practically impossible to teach good programming to students that have had a prior exposure to BASIC: as potential programmers they are mentally mutilated beyond hope of regeneration.

http://www.cs.virginia.edu/~cs655/readings/ewd498.html

The Manual wrote:
Relying on the default value of an uninitialized variable is problematic in the case of including one file into another which uses the same variable name. It is also a major security risk with [man]register_globals[/man] turned on. E_NOTICE level error is issued in case of working with uninitialized variables, however not in the case of appending elements to the uninitialized array. [man]isset/man language construct can be used to detect if a variable has been already initialized.

http://www.php.net/language.variables.basics