Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60491
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain oracolo.com designates 209.85.214.42 as permitted sender)
MIME-Version: 1.0
Sender: devis@oracolo.com
In-Reply-To: <CABBJUpcv1FFziR8jqm7VA9mvZ3Yw2X4JP2WqGAiULui-uzqHcA@mail.gmail.com>
References: <CAET_qdOGuKsaY256ZSqgta71pdo4u64EkBH2HhkVMwvgGPoSfQ@mail.gmail.com>
 <CABBJUpdEYCDqGYFNQrcvPOQ2i8_OO9qrNiC36SHGyd0aFhMZkw@mail.gmail.com> <CABBJUpcv1FFziR8jqm7VA9mvZ3Yw2X4JP2WqGAiULui-uzqHcA@mail.gmail.com>
Date: Sun, 6 May 2012 12:10:50 +0100
Message-ID: <CAET_qdMTRii630K6fKCovGHkBkKPfhr7xoxr24JqkkNbP86Lcw@mail.gmail.com>
To: Laruence <laruence@php.net>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=0015175ce0a63582f004bf5c37fa
Subject: Re: [PHP-DEV] catching exception using a variable passed by reference
From: devis@lucato.it (Devis Lucato)

--0015175ce0a63582f004bf5c37fa
Content-Type: text/plain; charset=UTF-8

Hi Laruence,

the solution you suggest would work though it makes it all a bit more
verbose...
I noticed also that the original variable is completely removed from the
function scope, which is probably a bug.
I'll raise a ticket, thank you ;-)

Devis



On 6 May 2012 05:04, Laruence <laruence@php.net> wrote:

> On Sun, May 6, 2012 at 11:47 AM, Laruence <laruence@php.net> wrote:
> > On Sun, May 6, 2012 at 8:40 AM, Devis Lucato <devis@lucato.it> wrote:
> >> Hi,
> >>
> >> I stumbled upon this code while working with a variable passed by
> >> reference, I was wondering if someone could provide some feedback before
> >> raising a ticket, just in case PHP (5.3.6) is doing what it's supposed
> to
> >> do.
> >> In the code below I would expect "catch" to change the variable as
> >> an assignment would do, but that doesn't happen.
> >>
> >>  function foo(&$exception)
> >>> {
> >>>     try {
> >>>         throw new Exception('foo error');
> >>>     } catch (Exception $exception) {
> >>>         var_dump(gettype($exception));
> >>>         echo $exception->getMessage() . "\n";
> >>>     }
> >>> }
> >>> foo($error);
> >>> var_dump(gettype($error));
> >>
> >>
> >>
> >> Expected:
> >>
> >>> string(6) "object"
> >>> foo error
> >>> string(6) "object"
> >>
> >>
> >> Current result:
> >>
> >>> string(6) "object"
> >>> foo error
> >>> string(4) "NULL"
> >>
> >>
> >>
> >> It looks like "catch" is creating a completely new variable in the
> scope,
> >> also removing the existing one from it.
> Hi:
>   after a deep look,  I think it's not a bug.
>
>   the exception in the catch block is only a local var of that block.
>
>   I think you should change you codes like following to accomplish
> your requirement:
>
>  function foo(&$exception)
> {
>    try {
>        throw new Exception('foo error');
>     } catch (Exception $e) {
>        var_dump(gettype($e));
>        $exception = $e;
>        echo $e->getMessage() . "\n";
>    }
> }
> foo($error);
> var_dump(gettype($error));
>
> thanks
> > Hi,
> >
> >    could you file a bug at bugs.php.net?  :)
> >
> > thanks
> >> I appreciate this is an edge case, if not a bug is it worth adding it to
> >> http://php.net/manual/en/language.exceptions.php or somewhere under
> >> http://www.php.net/manual/en/language.references.php ?
> >>
> >>
> >> Thank you!
> >
> >
> >
> > --
> > Laruence  Xinchen Hui
> > http://www.laruence.com/
>
>
>
> --
> Laruence  Xinchen Hui
> http://www.laruence.com/
>

--0015175ce0a63582f004bf5c37fa--