when using php operatpr @ what exactly happen to the errors in the script?

when using php operatpr @ what exactly happen to the errors in the script?
Nura111Asked:
Who is Participating?
 
Dave BaldwinConnect With a Mentor Fixer of ProblemsCommented:
They still exist, you just don't see them.  If they are 'fatal', your script will crash and you won't know why.
0
 
Nura111Author Commented:
ok I have a lamp web application on apache where notmally I would find the errors?
(unless im echoing them to the screen (e.g die(ShowError("Server Query Error"));)

      }
0
 
Ray PaseurConnect With a Mentor Commented:
Parse errors should still show up.  But if you try something like this:

$fp = @fopen('/path/to/nowhere', 'r');

and the file does not exist the value of $fp will be set to FALSE, however the warning will not be issued.

A principle to live by: Unless you know exactly what you are doing, and you expect errors, and you really want to suppress the messages, never use the @ notation.  
0
 
Nura111Author Commented:
I never seed the Parse errors should still show up in the web application im working on so isnt there is a log file they where they are suppose to be? Im confused about where would I suppose to see php wrrors in general because when Im testing things on lcalhost xmapp for expmple I see all error and warning on the screen  and in the web application I dont..
0
 
Ray PaseurConnect With a Mentor Commented:
Probably in the web application the errors are written to a log and 'display_errors' is set to FALSE
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.