Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:40255 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 73221 invoked from network); 4 Sep 2008 14:34:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Sep 2008 14:34:21 -0000 Authentication-Results: pb1.pair.com header.from=office@kitsoftware.ro; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=office@kitsoftware.ro; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain kitsoftware.ro from 81.196.12.70 cause and error) X-PHP-List-Original-Sender: office@kitsoftware.ro X-Host-Fingerprint: 81.196.12.70 smtp1.rdslink.ro Linux 2.4/2.6 Received: from [81.196.12.70] ([81.196.12.70:33209] helo=smtp.rdslink.ro) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 84/00-07417-BE1FFB84 for ; Thu, 04 Sep 2008 10:34:21 -0400 Received: (qmail 27501 invoked from network); 4 Sep 2008 14:34:17 -0000 X-Mail-Scanner: Scanned by qSheff 1.0 (http://www.enderunix.org/qsheff/) Received: from unknown (HELO AntauriPC) (86.121.161.176) by smtp1.rdslink.ro with SMTP; 4 Sep 2008 14:34:16 -0000 To: "'Diogo Neves'" Cc: "'PHP Internals List'" References: <000601c90e98$d5a57ca0$80f075e0$@ro> <000e01c90e99$94e04280$bea0c780$@ro> <87ae45950809040724q6660ea44xa527dc0670822333@mail.gmail.com> In-Reply-To: <87ae45950809040724q6660ea44xa527dc0670822333@mail.gmail.com> Date: Thu, 4 Sep 2008 17:33:47 +0300 Message-ID: <001501c90e9b$3dca7d10$b95f7730$@ro> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AckOmfYxXUeWQy4yTrCx9cXWZ6RKFwAAQJWw Content-Language: en-us Subject: RE: [PHP-DEV] Ob_start, "protected" obHandler method, nod detecting $this->geMe () kind of error! From: office@kitsoftware.ro ("Catalin Zamfir Alexandru | KIT Software CAZ") Yes, that's the "so-called bug" I'm talking about. Having the obHandler marked as "protected" makes "$this->getMe ()" kind of errors, from GLOBAL context undetectable, while Parse/Notice/Warning errors are stil there, even if the "$this->getMe ()" error is marked as "Fatal Error:". Here: Fatal error: Using $this when not in object context in /var/www/localhost/htdocs/dev/ALFA/index.php on line 26 (this is when obHandler = public). A blank page = when obHandler = protected, but Parse/Notice/any other kind of errors are still detected. :) -----Original Message----- From: Diogo Neves [mailto:dafneves@gmail.com] Sent: Thursday, September 04, 2008 5:24 PM To: Catalin Zamfir Alexandru | KIT Software CAZ Cc: PHP Internals List Subject: Re: [PHP-DEV] Ob_start, "protected" obHandler method, nod detecting $this->geMe () kind of error! On Thu, Sep 4, 2008 at 3:21 PM, Catalin Zamfir Alexandru | KIT Software CAZ wrote: > Yes, excuse my English would be appropriate. I was in a hurry when writing > the email. Waiting for feedback from you guys ... > > -----Original Message----- > From: Catalin Zamfir Alexandru | KIT Software CAZ > [mailto:office@kitsoftware.ro] > Sent: Thursday, September 04, 2008 5:17 PM > To: 'PHP Internals List' > Subject: [PHP-DEV] Ob_start, "protected" obHandler method, nod detecting > $this->geMe () kind of error! > > Hello guys, > > We have too clases: > > - Abstract class OutputBuffering > > - Class ErrorHandler extends OutputBuffering, implements obHandler > as a "protected" method. I can detect: set_error_handler errors, through a > specific error handler (and obError method - I can detect any > notice/warning/fatal) and also "Parse errors" in obHandler, through > "parsing" error_prepend/error_append strings in the Output Buffer string. > > > > When the obHandler methos is "protected", the "$this->getMe ()" from GLOBAL > context cannot be detected. When the method is "public", the detection goes > as usual. The MANUAL Page on "ob_start" doesn't say anything about > declaring > the method "public". What if I want the "obHandler" method to not be > accessible by the developer, but only by inheriting objects?! > > > > Thanks for any feedback. > > > > Regards, > > Catalin Z. Alexandru > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > Did you tried protected? I'm not really good with this things, but a protected method can be inherited but not acessed outside the class ;) -- Thanks, Diogo Neves Web Developer @ SAPO.pt by PrimeIT.pt