Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:55696 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 10302 invoked from network); 3 Oct 2011 20:26:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Oct 2011 20:26:08 -0000 Authentication-Results: pb1.pair.com smtp.mail=chrisstocktonaz@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=chrisstocktonaz@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.42 as permitted sender) X-PHP-List-Original-Sender: chrisstocktonaz@gmail.com X-Host-Fingerprint: 209.85.216.42 mail-qw0-f42.google.com Received: from [209.85.216.42] ([209.85.216.42:61992] helo=mail-qw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CB/60-07484-F5A1A8E4 for ; Mon, 03 Oct 2011 16:26:08 -0400 Received: by qadc12 with SMTP id c12so2232882qad.29 for ; Mon, 03 Oct 2011 13:26:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=l/IIsi9sP+uDEWz2DRlk5fVlT1LZ3AWLa58zvLvLxRU=; b=hdikKkZefDfHjKnu4e1kkUO6QPqroA5wU90ym6GrAMBmtrnUwoBeCZWdDQlZ64zFf0 OHQ8MqMLeamw2jbbi6AJCQDJvNeJKdcSksrCjWBTVCQPhihW98bt6sGLpKFqAhuAQhZC FMLpSrppnOjZet/hq92uY1KhMTiyp5hBvudrQ= MIME-Version: 1.0 Received: by 10.42.136.6 with SMTP id r6mr541741ict.35.1317673564481; Mon, 03 Oct 2011 13:26:04 -0700 (PDT) Received: by 10.42.170.132 with HTTP; Mon, 3 Oct 2011 13:26:04 -0700 (PDT) Date: Mon, 3 Oct 2011 13:26:04 -0700 Message-ID: To: PHP Developers Mailing List Content-Type: text/plain; charset=ISO-8859-1 Subject: Bug with static property access From: chrisstocktonaz@gmail.com (Chris Stockton) Hello, I noticed the following odd behavior earlier today, there is definitely a bug here in my opinion, the bug is either the error message or the behavior. I think the behavior is possibly expected. I'll let some others comment. The reason I think the error is odd is because it is very misleading in a much larger code base (what I was debugging) you go to the line it is complaining about and are perplexed because you are not attempting to access the mentioned constant. I'm sure the engine does some kind of lazy/runtime determination that causes this, that area may need a look at? Example: // prints string(17) "ClassA::MethodOne" Fatal error: Undefined class constant 'self::VERSION' in /testbug.php on line 14