Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:15405
Return-Path: <pollita@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 84679 invoked by uid 1010); 12 Mar 2005 18:54:14 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 84664 invoked by uid 1007); 12 Mar 2005 18:54:14 -0000
Message-ID: <20050312185414.84663.qmail@lists.php.net>
To: internals@lists.php.net
References: <4231F330.6000705@prohost.org> <4e89b426050311134633b22b@mail.gmail.com> <4232163C.1000906@prohost.org> <f0716b84ded9430aef38b6aa28eeb55d@at.wakwak.com> <4232D97B.5020305@cschneid.com>
Date: Sat, 12 Mar 2005 09:26:18 -0800
Lines: 14
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Response
X-Posted-By: 64.142.6.231
Subject: Re: [PHP-DEV] HALT Patch
From: pollita@php.net ("Sara Golemon")

> Hmm.. I was wondering if we should go one step further and also provide a 
> stream to the data. If the most common usage of this construct is going to 
> be reading the data after __HALT_PHP_PARSER__ then we should optimize for 
> that case. Something like
>
> <?php
> $data = gzdeflate(file_get_contents("php://data"));
> ?>
> <?php __DATA__; ?>
> ...
I think at that point this progresses from "unobtrusive lexer enhancement" 
into the realm of "magic voodoo fluffiness".