Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68546
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain bof.de designates 80.242.145.70 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <520D6758.4050500@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>
	<CAESVnVpj-+QosszvtttUH-vtkTUGvEa0MUf-rEGz_BijDta_SQ@mail.gmail.com>
	<520D6758.4050500@sugarcrm.com>
Date: Fri, 16 Aug 2013 09:43:00 +0200
Message-ID: <CAJ26g5SdY+5vUrbHL4e3SvHLaNhLmuo_qTLrQ1R0nFvoqFoYFw@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Julien Pauli <jpauli@php.net>, internals <internals@lists.php.net>, 
	Sebastian Krebs <krebs.seb@gmail.com>, Derick Rethans <derick@php.net>, 
	Anthony Ferrara <ircmaxell@gmail.com>, Sara Golemon <pollita@php.net>
Content-Type: multipart/alternative; boundary=089e01294a5067561c04e40bbd33
Subject: Re: [PHP-DEV] [RFC] Constant Scalar Expressions
From: bof@bof.de (Patrick Schaaf)

--089e01294a5067561c04e40bbd33
Content-Type: text/plain; charset=ISO-8859-1

Am 16.08.2013 01:42 schrieb "Stas Malyshev" <smalyshev@sugarcrm.com>:
>
> But this is not the most tricky part. The most tricky part is this:
> if(true) return;
> class Foo {
> const halfpie = M_PI/2;
> }
>
> Now what happens if this is implemented as an opcode? We can't run any
> opcodes past return statement, but Foo is expected to be defined here.

Couldn't the opcodes for such behind-the-scenes initialization be generated
as the first thing of the '(main)' opcode stream, so that they would run
before it comes to the "if (true) return;" ?

Once that is in place, make classes have an optional on-first-use opcode
stream, too:
- emit calls to that in the file's up-front opcode stream for each locally
defined class that has them
- in that per-class initializer stream, expression evaluation even for
non-constant initializers (protected $foo = anything::whatever()*10;) could
be put
- and also a call to the much talked about static class initializer function
- all in strict definition order, with fallout related to interdependance
left to confuse class authors :)

best regards
  Patrick

--089e01294a5067561c04e40bbd33--