Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59395
Return-Path: <tom@punkave.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 88975 invoked from network); 7 Apr 2012 13:26:35 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 7 Apr 2012 13:26:35 -0000
Authentication-Results: pb1.pair.com smtp.mail=tom@punkave.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=tom@punkave.com; 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:38756] helo=mail-gy0-f170.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 61/00-23111-F60408F4 for <internals@lists.php.net>; Sat, 07 Apr 2012 09:26:08 -0400
Received: by ghbg2 with SMTP id g2so1706085ghb.29
        for <internals@lists.php.net>; Sat, 07 Apr 2012 06:26:01 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type
         :x-gm-message-state;
        bh=lrkxZAWnfVEXfAVrGAr7NJkj8KtbbRM99BkWmE3qArk=;
        b=a/o0awbjR3HUcMh9Kz0LY+MyEPHT5RuWQq5XZPIvvSSJp144i9XBfzSp3yaNRA/gTt
         2SnTLr1v2kAm9VLjmYKSgzcwfRSZUkieaUvcC4Z0BiRb4q4EvVXB8/D7HUxOYoWe+VPt
         kCnGYFFRnQJ8QSSZJcMkxcCQ4augeW0t8ekRGbc2GJe95fOrwK2eJSiTkIkB8Q1rfbHV
         L8jwzMbc1LtEymkAw7TMwJikZO0IUkljtgDCVazSHfTlH6WDl4B7U92fKSTrwVqMLZvR
         BjrtPcdxWqP4XHZeeUQxQpvcD9wvmlagEe9OpqcJVGq9CEX2joQsh9quFOXwxGlq0D94
         9Y4Q==
MIME-Version: 1.0
Received: by 10.101.166.32 with SMTP id t32mr327495ano.41.1333805161296; Sat,
 07 Apr 2012 06:26:01 -0700 (PDT)
Received: by 10.100.35.16 with HTTP; Sat, 7 Apr 2012 06:26:01 -0700 (PDT)
Date: Sat, 7 Apr 2012 09:26:01 -0400
Message-ID: <CAORXhGLk8=bJ2TEo0OCzQCacjtGG=ZWYNuXf8Uu8oMNEm2WQ1A@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQnOtafL7YiM0mI3rauaQL9tLg5DRO73U4YEYdVigtc+plLD8rWzUmwfDW9ZsBD1SefdasdA
Subject: PHP class files without <?php at the top
From: tom@punkave.com (Tom Boutell)

Now that the flamewar has died down a little I'd like to try to have a
civil discussion about this idea - *without* my admittedly
inflammatory suggestion to kill <?php altogether.

So here is what I am seriously suggesting:

* The default behavior doesn't change. The parser starts out in HTML mode.

* If the CLI sees a .phpc file extension, the parser starts out in PHP
mode (no opening <?php is required). It is still possible to shift
into HTML mode after that with ?>.

* If a require/include statement sees a .phpc file extension, the
parser starts out in PHP mode.

* If mod_php and FPM are able to see the path (I'm honestly not sure
if they can or not), they look for .phpc as their indication to start
out in PHP mode. If that's not possible then new options are defined
to allow Apache to be configured to tell mod_php and/or FPM to do the
right thing based on mime types etc.

This way .php continues to behave exactly as it does today, and can
interoperate smoothly with code that uses .phpc. .phpc can require
.php and vice versa. They are friends.

Thoughts?

-- 
Tom Boutell
P'unk Avenue
215 755 1330
punkave.com
window.punkave.com