Home
About
Search
🌐
English Română
  • Finally finally in PHP 5.5

    Citește postarea în română

    May 19, 2013 finally PHP php5.5
    Share on:

    The newest PHP version is almost ready. At the time I’m writing this blog PHP 5.5 is in RC 1.

    As I was saying in my last blog, the feature list is available at: http://www.php.net/manual/en/migration55.new-features.php

    The second feature, in terms of popularity, is “finally“: http://www.php.net/manual/en/language.exceptions.php

    What’s the deal with “finally“?

    It looks a little confusing, is looks like a block that’s getting executed after the “try/catch” finishes. But what is so new about it?

    Let’s take a try/catch block:

    PHP 5.x < 5.5:

     1// open resouce
     2$resource = new Resouce();
     3try {
     4   // do stuff with the resouce
     5   $resouce->doStuff();
     6} catch (Exception $e) {
     7   // log exception
     8   syslog(LOG_ERR, $e->getMessage());
     9}
    10// release resouce
    11unset($resouce);
    

    PHP 5.5

     1// open resouce
     2$resource = new Resouce();
     3try {
     4   // do stuff with the resouce
     5   $resouce->doStuff();
     6} catch (Exception $e) {
     7   // log exception
     8   syslog(LOG_ERR, $e->getMessage());
     9} finally {
    10   // release resouce
    11   unset($resouce);
    12}
    

    Up to this point there isn’t any reason for a new block. The exception was catched, it was logged and continues.

    But let’s say there is a resource and we need to close it, and after that we need to throw an exception. One way this can be achieved is to release the resource in catch.

    But there is still the “successful” case, and we need to release it in that case also.

     1// open resouce
     2$resource = new Resouce();
     3try {
     4   // do stuff with the resouce
     5   $resouce->doStuff();
     6} catch (Exception $e) {
     7   // release resouce
     8   unset($resource);
     9   // perpetuate exception
    10   throw $e;
    11}
    

    Let’s complicate stuff even more, let’s say there are n exception types. It will result in n catch conditions, plus the successful case, and in all of these cases we need to free the resource. Not very efficient…

    Another way is to store the exception in a variable and, after the resource is released, to throw the exception, if that is the case.

     1// variable to store the exception
     2$exception = false;
     3
     4// open resouce
     5$resource = new Resouce();
     6try {
     7   // do stuff with the resouce
     8   $resouce->doStuff();
     9} catch (Exception $e) {
    10   $exception = $e;
    11}
    12
    13// release resouce
    14unset($resource);
    15
    16if($exception) {
    17   throw $exception;
    18}
    

    This is one way it is done right now. It’s working but it’s not clear that we are only trying to release the resource and continue our lives in peace.

    The PHP 5.5 way

    In the php.net manual:

    In PHP 5.5 and later, a finally block may also be specified after the catch blocks. Code within the finally block will always be executed after the tryand catch blocks, regardless of whether an exception has been thrown, and before normal execution resumes.

    Each time the block is executed, regardless if it was successful or not, finally will get executed. So, for the next example:

    1try {
    2    echo 'Do stuff' . PHP_EOL;
    3    throw new Exception('testing');
    4} finally {
    5    echo 'inside finally' . PHP_EOL;
    6}
    

    The output will be:

    1Do stuff
    2inside finally
    3
    4Fatal error: Uncaught exception 'Exception' with message 'testing' in...
    

    If we want to also catch the exception:

    1try {
    2    echo 'Do stuff' . PHP_EOL;
    3    throw new Exception('testing');
    4} catch (Exception $e) {
    5    echo 'do something with the exception' . PHP_EOL;
    6} finally {
    7    echo 'inside finally' . PHP_EOL;
    8}
    

    The output will be:

    1Do stuff
    2do something with the exception
    3inside finally
    

    And even if we take the particular case when we catch the exception and then throw it:

    1try {
    2    echo 'Do stuff' . PHP_EOL;
    3    throw new Exception('testing');
    4} catch (Exception $e) {
    5    echo 'do something with the exception' . PHP_EOL;
    6    throw $e;
    7} finally {
    8    echo 'inside finally' . PHP_EOL;
    9}
    

    It seems we prevented the finally block from getting executed? Well, not exactly…

    1Do stuff
    2do something with the exception
    3inside finally
    4
    5Fatal error: Uncaught exception 'Exception' with message 'testing' in...
    

    In other words, the finally block gets executed each time, regardless of the result.

Claudiu Perșoiu

Programming, technology and more
Read More

Recent Posts

  • Adding a slider to Tasmota using BerryScript
  • The future proof project
  • Docker inside wsl2
  • Moving away from Wordpress
  • Custom path for Composer cache
  • Magento2 and the ugly truth
  • A bit of PHP, Go, FFI and holiday spirit
  • How to make use of the Xiaomi Air Conditioning Companion in Home Assistant in only 20 easy steps!

PHP 49 MISCELLANEOUS 46 JAVASCRIPT 14 MAGENTO 7 MYSQL 7 BROWSERS 6 DESIGN PATTERNS 5 HOME AUTOMATION 2 LINUX-UNIX 2 WEB STUFF 2 GO 1

PHP 35 JAVASCRIPT 15 PHP5.3 11 MAGENTO 7 PHP6 7 MYSQL 6 PHP5.4 6 ZCE 6 CERTIFICARE 5 CERTIFICATION 5 CLOSURES 4 DESIGN PATTERNS 4 HACK 4 ANDROID 3
All tags
3D1 ADOBE AIR2 ANDROID3 ANGULAR1 ANONYMOUS FUNCTIONS3 BERRYSCRIPT1 BOOK1 BROWSER2 CARTE1 CERTIFICARE5 CERTIFICATION5 CERTIFIED1 CERTIFIED DEVELOPER1 CHALLENGE1 CHM1 CLASS1 CLI2 CLOSURES4 CODE QUALITY1 CODEIGNITER3 COFFEESCRIPT1 COLLECTIONS1 COMPOSER1 CSS1 DEBUG1 DESIGN PATTERNS4 DEVELOPER1 DEVELOPMENT TIME1 DOCKER2 DOCKER-COMPOSE1 DOUGLAS CROCKFORD2 ELEPHPANT2 FACEBOOK2 FFI1 FINALLY1 FIREFOX3 GAMES1 GENERATOR1 GO1 GOOGLE1 GOOGLE CHROME1 GOOGLE MAPS1 HACK4 HOMEASSISTANT2 HTML2 HTML HELP WORKSHOP1 HTML51 HUG1 HUGO1 INFORMATION_SCHEMA1 INI1 INTERNET EXPLORER3 IPV41 IPV61 ITERATOR2 JAVASCRIPT15 JQUERY1 LAMBDA1 LINUX1 MAGENTO7 MAGENTO22 MAP1 MINESWEEPER1 MOTIVATION1 MYSQL6 NGINX1 NODE.JS2 NOSQL1 OBSERVER3 OBSERVER PATTERN1 OOP1 OPERA1 OPTIMIZATION1 ORACLE1 PAGESPEED1 PAIR1 PARSE_INI_FILE1 PHONEGAP2 PHP35 PHP ELEPHANT2 PHP FOR ANDROID1 PHP-GTK1 PHP42 PHP53 PHP5.311 PHP5.46 PHP5.53 PHP5.61 PHP67 PHP7.41 PROGRAMMING1 REVIEW1 ROMANIAN STEMMER2 SAFARY1 SCALAR TYPE HINTING1 SCHEME1 SET1 SHOPPING CART PRICE RULE1 SINGLETON1 SOAP1 SPL2 SQLITE1 SSH1 STACK TRACE1 STDERR1 STDIN1 STDOUT1 SUN1 SYMFONY2 TASMOTA1 TEST TO SPEECH1 TITANIUM2 TRAITS1 TTS1 UBUNTU1 UNICODE2 UTF-82 VECTOR1 WEBKIT1 WINBINDER1 WINDOWS2 WORDPRESS1 WSL21 YAHOO3 YAHOO MAPS1 YAHOO OPEN HACK1 YSLOW1 YUI1 ZCE6 ZCE5.31 ZEND3 ZEND FRAMEWORK3
[A~Z][0~9]

Copyright © 2008 - 2024 CLAUDIU PERȘOIU'S BLOG. All Rights Reserved