Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:21975 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 58395 invoked by uid 1010); 21 Feb 2006 22:25:02 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 58379 invoked from network); 21 Feb 2006 22:25:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Feb 2006 22:25:02 -0000 X-Host-Fingerprint: 64.142.83.254 64-142-83-254.dsl.static.sonic.net Linux 2.5 (sometimes 2.4) (4) Received: from ([64.142.83.254:41793] helo=64-142-83-254.dsl.static.sonic.net) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id E3/10-45151-E339BF34 for ; Tue, 21 Feb 2006 17:25:02 -0500 Received: from localhost ([127.0.0.1] helo=localhost.localdomain) by 64-142-83-254.dsl.static.sonic.net with esmtp (Exim 4.43) id 1FBfwk-0006kk-O9 for internals@lists.php.net; Tue, 21 Feb 2006 14:25:26 -0800 Received: (from apache@localhost) by localhost.localdomain (8.13.1/8.13.1/Submit) id k1LMPQu0025961; Tue, 21 Feb 2006 14:25:26 -0800 X-Authentication-Warning: localhost.localdomain: apache set sender to mes@zeroc.com using -f Received: from 192.168.1.102 (SquirrelMail authenticated user mark); by 192.168.1.3 with HTTP; Tue, 21 Feb 2006 14:25:26 -0800 (PST) Message-ID: <1758.192.168.1.102.1140560726.squirrel@192.168.1.3> Date: Tue, 21 Feb 2006 14:25:26 -0800 (PST) To: "PHP Internals List" User-Agent: SquirrelMail/1.4.3a-12.EL4.centos4 X-Mailer: SquirrelMail/1.4.3a-12.EL4.centos4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Change to function call semantics in PHP 5.1? From: mes@zeroc.com ("Mark Spruiell") In PHP 5.0.x, I can chain function calls like this: $obj->method()->anotherMethod(); In PHP 5.1.x, this code results in an error: parse error, unexpected T_OBJECT_OPERATOR in ... I've looked through the change log for 5.1 but didn't see anything relevant. Was this an intentional change? Thanks, - Mark