Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60686
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zerocue.com designates 74.115.204.80 as permitted sender)
To: "internals@lists.php.net" <internals@lists.php.net>
Thread-Topic: zend_compile_string() usage within code
Thread-Index: Ac09R//ufjQ8HahrSJWX7nQbLixWvg==
Date: Tue, 29 May 2012 03:10:24 +0000
Message-ID: <9570D903A3BECE4092E924C2985CE48558639884@MBX202.domain.local>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_9570D903A3BECE4092E924C2985CE48558639884MBX202domainloc_"
MIME-Version: 1.0
Subject: zend_compile_string() usage within code
From: cpriest@zerocue.com (Clint Priest)

--_000_9570D903A3BECE4092E924C2985CE48558639884MBX202domainloc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Has anyone ever used the zend_compile_string() within the c code for compil=
ing internally created php?  Is it frowned upon or has it never come up bef=
ore?

In writing the accessors code I have several parts that are effectively jus=
t mimicking what a simple zend_compile_string() would accomplish in a singl=
e line.  It may be just as efficient as writing the zend_do_begin_variable_=
parse() ... etc lines myself but would have the added benefit of changing a=
s the language changed as well.

More specific example:

Automatic implementation for a getter, would be something like this:

public $a {
                get;  /* Equivalent to "return $this->__a */
                set;  /* Equivalent to "$this->__a =3D $value; */
}

I would simply CG(active_op_array) =3D zend_compile_string("return $this->_=
_a;", ...);

Thoughts?

-Clint


--_000_9570D903A3BECE4092E924C2985CE48558639884MBX202domainloc_--