Hudzilla.org - the homepage of Paul Hudson

24.18 Answers to Chapter 19

This is NOT the latest copy of this book; click here for the latest version.

"Assert() flags a warning when the condition specified is true: true or false" False: quite the opposite is true.
"Using @ to hide errors is good practice: true or false" False: only do it when you must, otherwise you're masking errors that are probably worth correcting.
"Name three reasons why you might receive the error, "Call to undefined function"" There are various reasons why this error and others like it might pop up: You might have named using an extension that isn't supported, spelling the function name wrong, trying to access a private function, forgotten to include the relevant file, or be in a safe mode environment where that function is disabled.

<< 24.17 Answers to Chapter 18		25 The future of PHP >>
Table of Contents

Want to see this stuff in print? PHP in a Nutshell takes the core topics covered here, adds in thousands of edits from the editorial team and myself, and combines them to make an unbeatable reference for PHP programmers at all levels.

My latest book has hundreds more tips on how to use PHP, Apache, and MySQL, plus Perl, Python, shell scripts, performance tuning, and more!

Be the first to add a comment to this chapter!

Add comment
Please note that by posting a comment here you are committing it to the public domain. This is important so that others can make use of your code themselves, and also so that I can incorporate helpful notes directly into the main text. Comments are limited to 2000 characters in length.

If you are reporting an error in the content, please tell me directly.