w3resource

PHP Exercises : Get the last occurred error

PHP : Exercise-20 with Solution

Write a PHP script to get the last occurred error.

Sample Solution: -

PHP Code:

<?php
echo $x;
  print_r(error_get_last());
?>

Sample Output:

Array                                                       
(                                                           
    [type] => 8                                             
    [message] => Undefined variable: x                      
    [file] => /home/students/0d0149c0-f42e-11e6-a8c0-b738b9f
f32f9.php                                                   
    [line] => 2                                             
)

Flowchart:

Flowchart: Get the last occurred error

Note: error_get_last() function returns an associative array describing the last error with keys "type", "message", "file" and "line". If the error has been caused by a PHP internal function then the "message" begins with its name. Returns NULL if there hasn't been an error yet.

PHP Code Editor:

Have another way to solve this solution? Contribute your code (and comments) through Disqus.

Previous: Arithmetic operations on character variables : $d = 'A00'. Using this variable print the following numbers.
Next: Write a PHP function to test whether a number is greater than 30, 20 or 10 using ternary operator.

What is the difficulty level of this exercise?

Test your Programming skills with w3resource's quiz.



PHP: Tips of the Day

Why shouldn't I use mysql_* functions in PHP?

The MySQL extension:

  • Is not under active development
  • Is officially deprecated as of PHP 5.5 (released June 2013).
  • Has been removed entirely as of PHP 7.0 (released December 2015)
  • This means that as of 31 Dec 2018 it does not exist in any supported version of PHP. If you are using a version of PHP which supports it, you are using a version which doesn't get security problems fixed.
  • Lacks an OO interface
  • Doesn't support:
    • Non-blocking, asynchronous queries
    • Prepared statements or parameterized queries
    • Stored procedures
    • Multiple Statements
    • Transactions
    • The "new" password authentication method (on by default in MySQL 5.6; required in 5.7)
    • Any of the new functionality in MySQL 5.1 or later

Since it is deprecated, using it makes your code less future proof.

Lack of support for prepared statements is particularly important as they provide a clearer, less error-prone method of escaping and quoting external data than manually escaping it with a separate function call.

Ref : https://bit.ly/2BIIsF0