Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77910
Return-Path: <rowan.collins@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 79166 invoked from network); 13 Oct 2014 08:32:55 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 13 Oct 2014 08:32:55 -0000
Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.172 as permitted sender)
X-PHP-List-Original-Sender: rowan.collins@gmail.com
X-Host-Fingerprint: 209.85.212.172 mail-wi0-f172.google.com  
Received: from [209.85.212.172] ([209.85.212.172:55078] helo=mail-wi0-f172.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 49/E0-06457-63E8B345 for <internals@lists.php.net>; Mon, 13 Oct 2014 04:32:55 -0400
Received: by mail-wi0-f172.google.com with SMTP id n3so6662632wiv.17
        for <internals@lists.php.net>; Mon, 13 Oct 2014 01:32:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=user-agent:in-reply-to:references:mime-version
         :content-transfer-encoding:content-type:subject:from:date:to
         :message-id;
        bh=tgvtXBRyklhigpqaAD4y3rYDUm8vsCYmPP4VgidESw8=;
        b=EkkXdjEOXHHPBN0ovbXluNSEkEh6+uzEAcvVtbo2KMFMJy7XGASBw6TURx+FSTgRUW
         +7iPAK+NE+Y8WqBqAwOvJMnqU4sTcHq5kOijj8PabHlfpIyhyZJlCgQ0fla+lwKQN/nB
         bBSvY2CGxYlCxtJVLiU8iOAd2NGC5TIJe5Q/9JdHASdJG9XsOHDgC9UMOTz4fmWiX+kP
         J0/VX021CWgsVtxyG8UHILmaKkOTGH6/okgQHIQfZeKtuAbNCKDDqIBJ18k4pPlvoJa/
         8mFegw9g+O6ZRcdd7FKjVXc8QirI3D6x6KuB5B/mnq3ekfk8/++V7JKtd6pZNh9yU0p3
         nyFQ==
X-Received: by 10.180.104.199 with SMTP id gg7mr18538792wib.46.1413189171960;
        Mon, 13 Oct 2014 01:32:51 -0700 (PDT)
Received: from [192.168.0.3] (cpc68956-brig15-2-0-cust215.3-3.cable.virginm.net. [82.6.24.216])
        by mx.google.com with ESMTPSA id lk6sm15795844wjb.26.2014.10.13.01.32.50
        for <multiple recipients>
        (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Mon, 13 Oct 2014 01:32:51 -0700 (PDT)
User-Agent: K-9 Mail for Android
In-Reply-To: <543B79E8.9030802@lsces.co.uk>
References: <CAF+90c-B74M82xOkT1VguqShE3b2W2YLJ1HX_XzCJtG_WUSxxg@mail.gmail.com> <alpine.DEB.2.11.1410120854210.4012@whisky.home.derickrethans.nl> <CAF+90c_3XdSYeTWpBcSNS7+QmAET2QjpGgNgs4X+8k77Z+1FYw@mail.gmail.com> <543B1E3D.5000500@gmail.com> <543B79E8.9030802@lsces.co.uk>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain;
 charset=UTF-8
Date: Mon, 13 Oct 2014 09:29:40 +0100
To: Lester Caine <lester@lsces.co.uk>,internals@lists.php.net
Message-ID: <A9B67CA8-41E3-4ECA-8873-A70750F0D484@gmail.com>
Subject: Re: [PHP-DEV] [RFC] Remove deprecated functionality in PHP 7
From: rowan.collins@gmail.com (Rowan Collins)

On 13 October 2014 08:06:16 GMT+01:00, Lester Caine <lester@lsces.co.uk> wrote:
>On 13/10/14 01:35, Rowan Collins wrote:
>>> Because ini files use ; for comments and not #.
>> 
>> - The behaviour of # as comments in earlier versions seems to have
>been
>> a side-effect of something else, rather than a deliberate feature. In
>> fact, it was possible to have a key starting with #, but a line
>starting
>> # that had no = was silently discarded. [4]
>
>Are there any examples where # is used in distributed ini files?
>Is this something that is related to someone's particular preference in
>style which a particular distribution path has changed every ; to # as
>a
>quick scan across my entire server base shows no cases where it is
>used.
>Certainly some projects have changed comment coding style in the code
>and irritatingly dropped docblock in favour of something else but I've
>not see any example of # based ini comments?

Based on the above, I think what happened is that people had used # for blocks of explanation, and ; for commented out values.

While hunting down what happened, I did find some downstream bugs from one Linux distro removing # comments in reaction to the deprecation notices, so this certainly wasn't just a localised mistake.