On Tuesday 24 April 2001 12:14, Svein Roar Nilsen wrote: > > beside, use @ in front of the command to pipe away the current error > > or stop on-screen display of errors in general. > > My problem is that not displaying anything in case of an error is a > completely unacceptable solution. I *MUST* return a valid XML message > in a predefined format. If not, I am violating the standard we are if (@foo_bar (42, 4711) == ERROR_CODE) { PrintXMLErrorMessage (); } else { GoOnProcessing (); } -- Christian Reiniger LGDC Webmaster (http://sunsite.dk/lgdc/) ...10001000110101011010101101011110111010113...???? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
- [PHP] Fatal Errors and Error Handling Svein Roar Nilsen
- Re: [PHP] Fatal Errors and Error Handling Geir Eivind Mork
- [PHP] Building as an Apache module Hasan Niyaz
- Re: [PHP] Fatal Errors and Error Handling Svein Roar Nilsen
- Re: [PHP] Fatal Errors and Error Handling Geir Eivind Mork
- Re: [PHP] Fatal Errors and Error Handl... Svein Roar Nilsen
- RE: [PHP] Fatal Errors and Error Handling Christian Reiniger
- RE: [PHP] Fatal Errors and Error Handling Boget, Chris
- Re: [PHP] Fatal Errors and Error Handling Christian Reiniger
- [PHP] no fetch Wilbert Enserink
- RE: [PHP] Fatal Errors and Error Handling Boget, Chris
- Re: [PHP] Fatal Errors and Error Handling Christian Reiniger
- RE: [PHP] Fatal Errors and Error Handling Boget, Chris
- Re: [PHP] Fatal Errors and Error Handling Christian Reiniger
- Re: [PHP] Fatal Errors and Error Handling Svein Roar Nilsen
- Re: [PHP] Fatal Errors and Error Handl... Christian Reiniger