Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59303
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.170 as permitted sender)
Message-ID: <4F786F1A.8000600@gmail.com>
Date: Sun, 01 Apr 2012 17:07:06 +0200
User-Agent: Thunderbird
MIME-Version: 1.0
To: Florian Anderiasch <ml@anderiasch.de>
CC: internals@lists.php.net
References: <4F7847CA.2090307@anderiasch.de>
In-Reply-To: <4F7847CA.2090307@anderiasch.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Question about parser implementation details
From: keisial@gmail.com (=?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?=)

On 01/04/12 14:19, Florian Anderiasch wrote:
> I'd appreciate any hints on how to tackle this serious concern.
You should launch a new thread to tackle them. You could then buy
foreign slaves to schedule them on their cores.

> Btw, in the spirit of x for hex and b for binary I thought about using
> this syntax:
>
> <?php
> $a = 0spqrMMXII; //set $a to 2012
> ?>
>
> unless anyone has any better suggestions?
Romans didn't have 0 in their keyboards. You should use a different
approach which didn't need such character.

Also, date extension needs to be extended to support ab urbe condita
dates. I think that's a more pressing concern.