Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68540
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.192.178 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <520BBA89.1090208@sugarcrm.com>
References: <CAAyV7nH4Uevngz7YH1=ZTZvOctU5h7ZMgRAQdBW8zYXpBCV2uA@mail.gmail.com>
	<CAMUwpuT12Cy7e5imTwS2oDOL-7rt6txqtXh7jm_1u5R0udMdLQ@mail.gmail.com>
	<520B4772.8090701@sugarcrm.com>
	<CAAyV7nH-+9U25GkpC0afgomR5T_7MPfCzvnhJLxOeZHuOL4=+A@mail.gmail.com>
	<CALtuQzDCunbtDtYbR1Qo+hWHH40prj=B59NJjgehy4x4BjU73Q@mail.gmail.com>
	<CAAyV7nFKrqqocC7vNV9N9Z=i5cgn=r7hQHw8Y_bsFfaEe6-Ubg@mail.gmail.com>
	<alpine.DEB.2.10.1308141425050.29410@whisky.home.derickrethans.nl>
	<520BBA89.1090208@sugarcrm.com>
Date: Thu, 15 Aug 2013 16:29:37 -0700
Message-ID: <CAESVnVpj-+QosszvtttUH-vtkTUGvEa0MUf-rEGz_BijDta_SQ@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Derick Rethans <derick@php.net>, Anthony Ferrara <ircmaxell@gmail.com>, 
	Sebastian Krebs <krebs.seb@gmail.com>, Julien Pauli <jpauli@php.net>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b674188f654ba04e404d8c4
Subject: Re: [PHP-DEV] [RFC] Constant Scalar Expressions
From: pollita@php.net (Sara Golemon)

--047d7b674188f654ba04e404d8c4
Content-Type: text/plain; charset=ISO-8859-1

I have mixed emotions on the yes/no side of things, but on the "how" side,
I think we can do this fairly easily.

During parse, when a non-scalar const expression is encountered, the actual
binding to the class is deferred, and bytecodes are emitted in the "(main)"
function.  To put it in psuedo-code terms:

<?php
class Foo {
  const bar = M_PI / 2;
}

Gets turned into:

<?php
class Foo { }
runkit_constant_add('Foo::bar', M_PI / 2);

Though obv, in reality we wouldn't use runkit_constant_add(), it'd be a new
opcode which had the same effect.  This is basically transparent to opcode
caches, allows the constant to actually change based on runtime conditions
(if you were foolish enough to make your constant so non-constant), and
leaves the syntax used by the user looking like a normal constant
declaration.

-Sara

--047d7b674188f654ba04e404d8c4--