Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93645
Return-Path: <keisial@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 25206 invoked from network); 31 May 2016 02:06:39 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 31 May 2016 02:06:39 -0000
Authentication-Results: pb1.pair.com header.from=keisial@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=keisial@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.48 as permitted sender)
X-PHP-List-Original-Sender: keisial@gmail.com
X-Host-Fingerprint: 74.125.82.48 mail-wm0-f48.google.com  
Received: from [74.125.82.48] ([74.125.82.48:37694] helo=mail-wm0-f48.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id E8/84-26200-EA1FC475 for <internals@lists.php.net>; Mon, 30 May 2016 22:06:39 -0400
Received: by mail-wm0-f48.google.com with SMTP id z87so88767294wmh.0
        for <internals@lists.php.net>; Mon, 30 May 2016 19:06:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-transfer-encoding;
        bh=aAEvq+Do2499ocN104bKog8vppmukcOsZDZNAnR/Vbc=;
        b=bmjMS9YEFf3dBuB8fGDDPItU/BfJWj2gcV063AkxuZOMvnMXn8AsgsJ8qfDrVkhVwx
         WIJPBHkBxjhNq02GPLoNwC9hpi9ZBc3ie0Ite/I6tlHaaivfm6whcPfVNw7p6/b09Euf
         gSGCc20pb3Vu8YQpeetFS2jkAmn3KktIvVR+s0eSApfzejyj3Xe8VQTytdqZ9JPG9FBn
         7ZELM4SbmMwm5P2C2r+BOp+DYthM7b3yHpmP2jq/eRblV6Od8DhFBICcMrKQH/pScy1z
         uSLDL39e1wjQPhuaB9oRmz96VFtn7TcqWyWOC/iBoxRPGeMdmZ5URsAGbUv8vQ/EgUHN
         SnmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to
         :subject:references:in-reply-to:content-transfer-encoding;
        bh=aAEvq+Do2499ocN104bKog8vppmukcOsZDZNAnR/Vbc=;
        b=F09H2WAyL22nHQTZ1yVhzKTnsM/wdUKaMnK9U1Ghc7be4SjEI39IMFy0mHqlkkyxqq
         JYVMgesWG72Z83s71Cpqj25gwZqY/VsYxbW0MLOi9S/g+OCEXpZ6FkMyc2+dXMfQvp0o
         hEbAb4d4W7TO4X3RjG0vyb5RsW3tzWk+19gMcS1hMOTy8pShpsMUSbLYGkGhN56NEO7o
         MdPoN1FGGV8sZJzr05JkuMzHYpwNbnGOQcXknVda3+bFEIGp0Y9ewuY/lywYScGyfpNo
         Ftp81gftUlvMeiuEdv9uPVRj9z8D05qR2PBxzomGAMgvxkTwhBCYCUMUl5lxkCzTeXm2
         kdIw==
X-Gm-Message-State: ALyK8tKdGzGU/gW87iC00XWwOaqAzU0qadVQ60DTMZHWXm06Npb1541nlMKP3Ax3IGmfWQ==
X-Received: by 10.194.102.202 with SMTP id fq10mr5154954wjb.153.1464660395452;
        Mon, 30 May 2016 19:06:35 -0700 (PDT)
Received: from [192.168.1.27] (53.red-88-27-117.staticip.rima-tde.net. [88.27.117.53])
        by smtp.gmail.com with ESMTPSA id uq7sm12326421wjc.19.2016.05.30.19.06.34
        for <internals@lists.php.net>
        (version=TLSv1/SSLv3 cipher=OTHER);
        Mon, 30 May 2016 19:06:34 -0700 (PDT)
Message-ID: <574CF1A8.10509@gmail.com>
Date: Tue, 31 May 2016 04:06:32 +0200
User-Agent: Thunderbird
MIME-Version: 1.0
To: internals@lists.php.net
References: <CALYT1Yo97rG=onQPoVC8Mt9qhScdDfk9KYuKAmKyzK=7U3TfcA@mail.gmail.com>
In-Reply-To: <CALYT1Yo97rG=onQPoVC8Mt9qhScdDfk9KYuKAmKyzK=7U3TfcA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] PHP's handling of BOM (byte order mark)
From: keisial@gmail.com (=?UTF-8?B?w4FuZ2VsIEdvbnrDoWxleg==?=)

On 31/05/16 02:33, Sammy Kaye Powers wrote:
> BOM's should not be treated as characters and should not be sent to
> the output. Is there any reason this should be considered the expected
> behavior? If not, I'd like to create an RFC to change it. :)

What about
«Hello Foo!
Today is <?= date("d F Y") ?>» ?

If there's a BOM, should it be sent?