Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:60292 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 60132 invoked from network); 24 Apr 2012 20:26:55 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Apr 2012 20:26:55 -0000 Authentication-Results: pb1.pair.com header.from=tom@punkave.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tom@punkave.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain punkave.com designates 209.85.160.170 as permitted sender) X-PHP-List-Original-Sender: tom@punkave.com X-Host-Fingerprint: 209.85.160.170 mail-gy0-f170.google.com Received: from [209.85.160.170] ([209.85.160.170:51786] helo=mail-gy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E8/F0-54790-F8C079F4 for ; Tue, 24 Apr 2012 16:26:55 -0400 Received: by ghbg2 with SMTP id g2so812767ghb.29 for ; Tue, 24 Apr 2012 13:26:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding:x-gm-message-state; bh=7OEeiEzCcYFjFWC59isD+Fbu+RVoejV0Y5UgQT33x+Q=; b=NnJCxrzsp9dGBbHNE6ZmeEEfq6Q9U9CCYNff9ZpEIgMhBqncig/7Lz2RQoqqo8K9dU JuJHcxhwojNv/8wkdbS6KsuYUwwkSPXGETKCzcR9ThL1jwEQLFB79TbaYmSKWQo+senl RnsWpSSnmAFOd1dcPATpX5pn+UY1KpjtET7E8cEsByl1wiqtfo2QnEuqZEy7vc58vweT 8uFf3y0AYZoyYDkb27kQruSrhwR1kbt6QadOCYICNOmnLB/4UhWdHYd8EPaUVeQi53KN H56AgS/WHrUUwltOyjWW5c6Ir7DzT8fGdMd00ZsJCdU7Do+sY4RVOlNB2YQFxAcNmUM0 Ikew== MIME-Version: 1.0 Received: by 10.236.175.164 with SMTP id z24mr20008092yhl.101.1335299212471; Tue, 24 Apr 2012 13:26:52 -0700 (PDT) Received: by 10.101.57.14 with HTTP; Tue, 24 Apr 2012 13:26:52 -0700 (PDT) In-Reply-To: References: Date: Tue, 24 Apr 2012 16:26:52 -0400 Message-ID: To: PHP Internals Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQlmAQ+MK6WKv3YIe0m7f41EemfbrBiFpgVXQZW2NM6YqjuEK426GNBG/kzlltFgofv9ucdv Subject: Re: [PHP-DEV] [RFC] Pure PHP Scripts (Updated) From: tom@punkave.com (Tom Boutell) That's a good point, it should say the PHP tokenizer, or something to that effect (folks who spend more time with the internals could say better what to call it). The major difference from his previous version of the RFC is his addition of the .phpf format, which would allow including a .php file with in it from a .phpf file, but would not allow or need any usage of within the .phpf file itself. On Tue, Apr 24, 2012 at 4:14 PM, Arvids Godjuks wrote: > As far as I read there is no difference from the previous RFC - it > says essentially the same. > > " The to, in essence, "switch to PHP mode" and start parsing the data as PHP co= de. > When the ?> tag is reached, the webserver "switches back" and resumes > parsing it as HTML. If no tags are given, the webserver will parse the fi= le > data as HTML code until a > I'm I the only one who thinks that this is just plain wrong? I know for a > fact that there is no "PHP mode" on the WEB server level. I think I > understand what it tries to say, but I totally disagree with what is > written and don't want to guess anything. > > 24 =C1=D0=D2=C5=CC=D1 2012 =C7. 22:52 =D0=CF=CC=D8=DA=CF=D7=C1=D4=C5=CC= =D8 Kris Craig =CE=C1=D0=C9=D3=C1=CC: > >> Hi all, >> >> I finally found some time today to update the RFC based on discussions >> here. Please have a look and let me know if I missed anything or if >> there's anything else that needs clarifying: >> >> https://wiki.php.net/rfc/phpp >> >> >> I also want to know if this is sufficient to satisfy some of the concern= s >> that have been raised about being able to implement this into existing >> frameworks that use a more "tangled" architecture. >> >> Thanks! =3D) >> >> --Kris >> --=20 Tom Boutell P'unk Avenue 215 755 1330 punkave.com window.punkave.com