Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125798
Content-Type: multipart/alternative;
 boundary="------------sCDbbprVH51MccTTssbQCu5z"
Message-ID: <b1b23215-6353-42c1-8181-aff2af609166@scriptfusion.com>
Date: Mon, 14 Oct 2024 10:03:39 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] Asymmetric visibility is a BC break
To: Valentin Udaltsov <udaltsov.valentin@gmail.com>
Cc: internals@lists.php.net
References: <CAPyeZ4N8GMiLNVCDGxdofcy6txBhng_i2UKUGpiS5bnZ-YcYvA@mail.gmail.com>
 <2A7CF24F-3AE3-4125-965F-C65431C42DFB@gmail.com>
 <CAPyeZ4MSc=Sw9UE0soCdBEnVAJ8wXHHhYqm88OffkvNLrHPxFw@mail.gmail.com>
 <e966cf16-794d-4827-9a5e-b0de780a5b91@app.fastmail.com>
 <30a41608-a1ea-40a9-8d2a-c53c508cd89f@jnvsor.net>
 <a6cdfe39-2a18-40b1-8da5-f49e9e7a7918@app.fastmail.com>
 <CAMrTa2FM4o6q8TXdBbuHfnD66vtqFBVL2Hw6_412Bf1r2T1QMg@mail.gmail.com>
 <CAPyeZ4M0LDzPBTjT_Qa-ccB73DNatGWdARg-mKMO1T1XmnTzUg@mail.gmail.com>
 <3648840e-5c73-49c9-bc89-105ed761e5c2@scriptfusion.com>
 <CAPyeZ4Ntw7LME-CSjS8Z2OGPshpKDtfnUA78zR0YtcUFVkH31w@mail.gmail.com>
Content-Language: en-GB
In-Reply-To: <CAPyeZ4Ntw7LME-CSjS8Z2OGPshpKDtfnUA78zR0YtcUFVkH31w@mail.gmail.com>
From: bilge@scriptfusion.com (Bilge)

This is a multi-part message in MIME format.
--------------sCDbbprVH51MccTTssbQCu5z
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 14/10/2024 02:51, Valentin Udaltsov wrote:
> Hi, Bilge!
>
> I think that PHP should then clearly explain what is a BC break and
> what isn't on a separate php.net page.
> And even explain what php version constraints are safe for Composer libraries.
>
> Some languages have such a document:
> -https://go.dev/doc/go1compat
> -https://peps.python.org/pep-0387/

Absolutely! After some 16 years using PHP, I only recently became aware 
BC breaks are acceptable in minor versions. For anyone spending 
significant time in open source, I think there is a tendency to become 
semver-minded and naturally assume PHP follows the same; it does not.

Cheers,
Bilge

--------------sCDbbprVH51MccTTssbQCu5z
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 14/10/2024 02:51, Valentin Udaltsov
      wrote:<span style="white-space: pre-wrap">
</span><span style="white-space: pre-wrap">
</span></div>
    <blockquote type="cite"
cite="mid:CAPyeZ4Ntw7LME-CSjS8Z2OGPshpKDtfnUA78zR0YtcUFVkH31w@mail.gmail.com">
      <pre wrap="" class="moz-quote-pre">Hi, Bilge!

I think that PHP should then clearly explain what is a BC break and
what isn't on a separate php.net page.
And even explain what php version constraints are safe for Composer libraries.

Some languages have such a document:
- <a class="moz-txt-link-freetext" href="https://go.dev/doc/go1compat">https://go.dev/doc/go1compat</a>
- <a class="moz-txt-link-freetext" href="https://peps.python.org/pep-0387/">https://peps.python.org/pep-0387/</a>
</pre>
    </blockquote>
    <p>Absolutely! After some 16 years using PHP, I only recently became
      aware BC breaks are acceptable in minor versions. For anyone
      spending significant time in open source, I think there is a
      tendency to become semver-minded and naturally assume PHP follows
      the same; it does not.</p>
    <p>Cheers,<br>
      Bilge<br>
    </p>
  </body>
</html>

--------------sCDbbprVH51MccTTssbQCu5z--