Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:58675 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 38956 invoked from network); 6 Mar 2012 16:40:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Mar 2012 16:40:13 -0000 Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.170 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.216.170 mail-qy0-f170.google.com Received: from [209.85.216.170] ([209.85.216.170:42610] helo=mail-qy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A5/58-32184-DED365F4 for ; Tue, 06 Mar 2012 11:40:13 -0500 Received: by qcmt36 with SMTP id t36so2987578qcm.29 for ; Tue, 06 Mar 2012 08:40:10 -0800 (PST) Received-SPF: pass (google.com: domain of tyra3l@gmail.com designates 10.224.116.74 as permitted sender) client-ip=10.224.116.74; Authentication-Results: mr.google.com; spf=pass (google.com: domain of tyra3l@gmail.com designates 10.224.116.74 as permitted sender) smtp.mail=tyra3l@gmail.com; dkim=pass header.i=tyra3l@gmail.com Received: from mr.google.com ([10.224.116.74]) by 10.224.116.74 with SMTP id l10mr8849378qaq.42.1331052010208 (num_hops = 1); Tue, 06 Mar 2012 08:40:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=E23YmpyfEcEdnvrDLSXuRwVEjN/2qCbCLHHyCOdpxlI=; b=XKfc4LPrA3aZrIMeQFle5xrV+n8LCMnQhi4BtWWt8L99YSUdR8vmtleTxSLIJfzzo9 ciD/kOdTQPeJBW02iK1e18jj5nzxGV8cgtDhDAmvvzSPJj7vavlrMnoR4JQ1Mrirhrq+ FWpDWlIONE0jwHwgESrAHST5RasBoolWlcF0kXASz6oEAJHpM0Y1B1/vxwA9tSgrhCkb rouDe02Oz6I0EI6U+VY4xL2HTudPR5X5uG2uIfm3qUeHyf5bOVizPFiJVCZKesRL0MMo ExHcNDwmyyBLBk3FwaaWd3fMPG9hG6zxiK/h7uBXR7F6/9bwFJVVHalw5pALCaV9NYUj vaoQ== MIME-Version: 1.0 Received: by 10.224.116.74 with SMTP id l10mr7638192qaq.42.1331052005070; Tue, 06 Mar 2012 08:40:05 -0800 (PST) Received: by 10.229.232.207 with HTTP; Tue, 6 Mar 2012 08:40:05 -0800 (PST) In-Reply-To: References: Date: Tue, 6 Mar 2012 17:40:05 +0100 Message-ID: To: Michael Morris Cc: PHP Internals List Content-Type: multipart/alternative; boundary=20cf306f76bcf0977f04ba95b1bb Subject: Re: [PHP-DEV] [RFC] Namespace and Parse tags on Include and Require From: tyra3l@gmail.com (Ferenc Kovacs) --20cf306f76bcf0977f04ba95b1bb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > > > The first is boolean - whether to look for php tags of any sort in the > file. The default needs to be to expect them, this is the backwards > compatible behavior, and I'm thinking this should be 0. 1 means "no > tags in file". This means the file to be included can be written > without any php tags at all. This might allow the parser to speed up, > but that would be a side benefice to two goals. > I don't like this, I mean one can end up printing out his sourcecode if - those files are publically available through the document root or - if he somewhere used a wrong argument, and includes a tagless file with the (default) with-tags option. on the other hand, a html file page with php code examples (but without php tags) could be turned into executing those examples if the tagless option is used. I would support the namespace option though. --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --20cf306f76bcf0977f04ba95b1bb--