Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:36278 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 51018 invoked from network); 21 Mar 2008 20:17:55 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Mar 2008 20:17:55 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.186 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.198.186 rv-out-0910.google.com Received: from [209.85.198.186] ([209.85.198.186:3970] helo=rv-out-0910.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A5/3A-26785-3F714E74 for ; Fri, 21 Mar 2008 15:17:55 -0500 Received: by rv-out-0910.google.com with SMTP id k15so911886rvb.23 for ; Fri, 21 Mar 2008 13:17:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=tacRV6C+97OiErH23uM/5LXXDtiER9m8s6r3jOasP/U=; b=Dyo7jhi+Zt6kfXDfoN0+NPMcdgB/L/OXHaRNYf+vk0YUg8aPEe6A3sw41NiA8iKnirjyIiiXAiTfIG9d2YN8Rlf5BE3GDi/2FjidgRDOLGZ3cAv/w+q0uGf/DN7ddAP4yF4rDPv7bP7BrALUOS/0Lx9rcXq+VlzyHeKLu0uImOU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=iKnJpA9NTpkI37/rSHHO5IM/76w5Jm+ynVNTrFQJMnNfBQAArbDn03mklcX0POh+GOIKa07yJ64Wvb5fk2ohPN+X0L+jw/yrGSLUpRtVP4lZl0+gYI0zYq72NbbHM/5Q3xVdVCei3T+IHf1Y7Ov2gGJoZUUvnCe1c5Whdli5DDY= Received: by 10.140.127.20 with SMTP id z20mr1613067rvc.77.1206130672786; Fri, 21 Mar 2008 13:17:52 -0700 (PDT) Received: by 10.141.116.12 with HTTP; Fri, 21 Mar 2008 13:17:52 -0700 (PDT) Message-ID: Date: Fri, 21 Mar 2008 21:17:52 +0100 To: "Stanislav Malyshev" Cc: jani.taskinen@iki.fi, "Marcus Boerger" , "PHP Internals" In-Reply-To: <47E414FD.4040608@zend.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47E3F714.60302@zend.com> <883216194.20080321193140@marcus-boerger.de> <47E40848.1060103@zend.com> <47E40C3F.8040601@sci.fi> <47E40E6E.5030103@zend.com> <47E414FD.4040608@zend.com> Subject: Re: [PHP-DEV] short_open_tag From: pierre.php@gmail.com ("Pierre Joye") On Fri, Mar 21, 2008 at 9:05 PM, Stanislav Malyshev wrote: > > The main reason is that they are not valid processing instructions. > > See http://www.w3.org/TR/REC-xml/#sec-pi > > Great, they are also probably not valid S-expressions and not valid > phrases in Mandarin. Why they are bad because of that? Is there any > requirement for them to be? PHP works more and more in a multi cultural environment (php, jsp, xml, etc.). One of the goals of a standard is to avoid conflicts, buggy behavior or system specific features. PHP works with XML in many cases, xhtml growing usage is one good example. I'm very surprised to have to discuss this problem once again in this list. Cheers, -- Pierre http://blog.thepimp.net | http://www.libgd.org