Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:51126
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain darkrainfall.org from 208.97.132.119 cause and error)
DomainKey-Status: bad (key type)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=darkrainfall.org; h=subject
	:mime-version:content-type:from:in-reply-to:date:cc
	:content-transfer-encoding:message-id:references:to; q=dns; s=
	darkrainfall.org; b=qkGSOPvE9kfDo8FDHrFhCxOSQW0bZKw6U2pN8d825I/a
	VyvjES2ZBGqVqXSzotaoqjF07XcXvfykhls8xXSJ9JX2x3FVpGFIf2xozVihNd+l
	jCdMCSjMwa+jKyKMwHuxnaUOckmy3X5cioyAFlZMRfHlU1mlw1at2P1sOabO1/c=
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <AANLkTi=U0m-tgKgbjvZRFNT-e7KYPrjY3PhqhXFTD3SK@mail.gmail.com>
Date: Wed, 22 Dec 2010 17:28:09 -0500
Cc: Scott MacVicar <scott@macvicar.net>,
 Stas Malyshev <smalyshev@sugarcrm.com>,
 "internals@lists.php.net" <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <A40EC57A-0B98-48F2-8BCD-FFE5F3892911@darkrainfall.org>
References: <AANLkTimMZf8aG=H4gBBjATEqkm+wQmGUBDLcH6-kLr5B@mail.gmail.com> <4D1254DF.9050704@sugarcrm.com> <AANLkTi=+wJ1xTaZveJ0avDyHUsK47mOphFJBvLs-qUpB@mail.gmail.com> <A51E272A-521D-4277-906C-25EF18752237@macvicar.net> <AANLkTi=U0m-tgKgbjvZRFNT-e7KYPrjY3PhqhXFTD3SK@mail.gmail.com>
To: Mathias Grimm <mathiasgrimm@gmail.com>
Subject: Re: [PHP-DEV] RFC - MACRO
From: gwynne@darkrainfall.org (Gwynne Raskind)

On Dec 22, 2010, at 4:38 PM, Mathias Grimm wrote:
> People always will want more, but some features are nice.
> for C/C++ programmers, macro is on of the best things to make thing =
work
> every where.
>=20
> its possible to create a IDE macro, but the native php feature will be =
good.
> template engines can de wrap this functionality too.
> is just like a variable:

I've long wished for preprocessing in PHP. It would be semi-trivial to =
plug in libcpp from GCC or llvm's preprocessing library, if licensing =
weren't an issue. If it is, then a reasonable homegrown implementation =
of C's preprocessor semantics, or at least a subset of them, isn't that =
difficult.

Piping through cpp has two major problems:
1) It's an extra runtime step. Slower, more error-prone, not always an =
option (shared hosting anyone?).
2) cpp doesn't understand # comments, single-quoted strings, heredocs, =
etc. Many PHP scripts therefore produce annoying/confusing errors.

Some issues with PHP-native preprocessing:
- Are eval() strings subject to it? At what stage, outer script =
processing or the eval string?
- #include/#import versus include()/require() - confusing
- Does preprocessing take place outside whatever PHP tags are active?

> On Wed, Dec 22, 2010 at 7:08 PM, Scott MacVicar <scott@macvicar.net> =
wrote:
>> I really dislike this, what about resolving orders, then people will =
want
>> undef, then ifdef with conditions.
>>=20
>> The language doesn't need to introduce anything that makes it more =
complex
>> to use.
>>=20
>> - Scott
>>=20
>> On 22 Dec 2010, at 11:55, Mathias Grimm <mathiasgrimm@gmail.com> =
wrote:
>>> I Just want a simple replace-on-the-air to avoid spend time writing =
more.
>>>=20
>>>=20
>>> On Wed, Dec 22, 2010 at 5:43 PM, Stas Malyshev =
<smalyshev@sugarcrm.com
>>> wrote:
>>>=20
>>>> Hi!
>>>>=20
>>>>=20
>>>> I want to request a C/C++ feature that i think is good.
>>>>>=20
>>>>> MACRO
>>>>>=20
>>>>=20
>>>> You know that you could write:
>>>> <?php
>>>> #define PF private function
>>>> #define SCOPE_CLASS(x) class MyProject_ ## x
>>>>=20
>>>>=20
>>>> class UseMacro
>>>> {
>>>>  PF preSave($object)
>>>>  {
>>>>     //...
>>>>  }
>>>>=20
>>>> }
>>>>=20
>>>> SCOPE_CLASS(Internal)
>>>> {
>>>>=20
>>>> }
>>>>=20
>>>> And then run it through CPP (gcc -Mcpp -E - - < in.php > out.php) =
and
>> get
>>>> all the macros processed?
>>>> --
>>>> Stanislav Malyshev, Software Architect
>>>> SugarCRM: http://www.sugarcrm.com/
>>>> (408)454-6900 ext. 227
>>>>=20
>>=20

-- Gwynne