Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44714 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 14501 invoked from network); 6 Jul 2009 02:49:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Jul 2009 02:49:49 -0000 Authentication-Results: pb1.pair.com smtp.mail=ben@vuetec.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ben@vuetec.com; sender-id=pass; domainkeys=good Received-SPF: pass (pb1.pair.com: domain vuetec.com designates 217.158.164.148 as permitted sender) DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: ben@vuetec.com X-Host-Fingerprint: 217.158.164.148 mx0.vuetec.com Received: from [217.158.164.148] ([217.158.164.148:38807] helo=mx0.vuetec.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FB/28-07609-946615A4 for ; Sun, 05 Jul 2009 22:49:47 -0400 Received: from mx0.vuetec.com (localhost [127.0.0.1]) by mx0.vuetec.com (Postfix) with ESMTP id CB35C1E9D6D for ; Mon, 6 Jul 2009 02:49:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=vuetec.com; h=from:to :subject:date:message-id:mime-version:content-type: content-transfer-encoding; s=selector1; bh=3OhogG8RXvhv9olFJfLzp hE2WIU=; b=u1QbWzrKCryXIWsIWO9toZQQGNafirKTa4aGmdsTjvf7wtZSzu9sj 75pQKe9Dplt8DhuqKPzRJEMMdXdcRkI9A== DomainKey-Signature: a=rsa-sha1; c=nofws; d=vuetec.com; h=from:to:subject :date:message-id:mime-version:content-type: content-transfer-encoding; q=dns; s=selector1; b=dMzObKOU1cExE+x T6byf+eVuxGBmbXfGrvHDxfiFdy0aBCH3wE8z/FGxaY9JFPuEaphEI1uK0TxJBY1 MjPVDaA== Received: from mx0.vuetec.com (localhost [127.0.0.1]) by mx0.vuetec.com (Postfix) with ESMTP id A5ECC61F3F for ; Mon, 6 Jul 2009 02:49:41 +0000 (UTC) Received: from BenPC (unknown [202.172.125.63]) by mx0.vuetec.com (Postfix) with ESMTP id 547F31E9D6D for ; Mon, 6 Jul 2009 02:49:39 +0000 (UTC) To: Date: Mon, 6 Jul 2009 12:49:39 +1000 Message-ID: <01cf01c9fde4$695ec880$3c1c5980$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 thread-index: Acn95BqnQ2yVGUehRGCpRyhiQB9mxg== Content-Language: en-au X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) Subject: autoloading and undefined class constants From: ben@vuetec.com ("Ben Bidner") Hi folks, Just looking for a quick clarification on how class constant look ups are performed internally under circumstances when an autoload function is also called. Consider the following example: I would have assumed that since the autoloader threw an exception while attempting to load the non existant class, that internally, there would be no attempt to access the non existant constant (since surely that comes after the exception was thrown???) and we would get the Exception, rather than a Fatal error. Intended or a design error? Ben Bidner +61.7.3161.2000 (office) | +61.7.3009.0651 (fax) | +61.4.3201.5362 (mobile) http://www.vuetec.com/