Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123643
Feedback-ID: id5114917:Fastmail
Content-Type: multipart/alternative;
 boundary="------------b3mOlOLD6SS0aBuhj3gAH4GY"
Message-ID: <c05a85a9-0b63-4a27-a72d-d3a2b5cf73ea@rwec.co.uk>
Date: Sun, 16 Jun 2024 19:07:53 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] Static class
To: internals@lists.php.net
References: <0cf69a14-f1b5-4077-9d91-d7b579485eec@scriptfusion.com>
 <936e1aa3-48cc-4552-9f68-676ebcdeb596@rwec.co.uk>
 <1fc2f2d0-718f-45ec-8968-b66a1bde686e@scriptfusion.com>
 <c2472dca-a297-4f14-bf53-b0ab9a67d3c7@rwec.co.uk>
 <b6d67db7-6689-4a1c-ad62-32cc96a01392@scriptfusion.com>
 <CAPyeZ4NW3eoaaXonM8bTHmji0a=CpWx7m8B5h_X44-eFDfOQbw@mail.gmail.com>
 <D53A9527-EE4B-4DC2-9CA4-A982EF236917@rwec.co.uk>
 <adb0e17c-c5b8-4e82-9d78-b09355f8a5fa@app.fastmail.com>
 <CAB-BujYmFxyNQV0-PZYz72A8CUHnkVvuHwPBvtOiBO9vV7+uDQ@mail.gmail.com>
 <4e439377-5c20-40d7-bb99-5d0ac6c348e9@rwec.co.uk>
 <CAB-BujZF83_kZYsyWkMAjbowCfSmSaZ7OZebyOG_BNP1S+CGFw@mail.gmail.com>
Content-Language: en-GB
In-Reply-To: <CAB-BujZF83_kZYsyWkMAjbowCfSmSaZ7OZebyOG_BNP1S+CGFw@mail.gmail.com>
From: imsop.php@rwec.co.uk ("Rowan Tommins [IMSoP]")

This is a multi-part message in MIME format.
--------------b3mOlOLD6SS0aBuhj3gAH4GY
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 16/06/2024 18:54, Andreas Hennings wrote:
> Yes, the possibility for namespace part imports exists.
> Unfortunately these namespace imports usually need to be set up
> manually, whereas the regular class or function import has better
> automatic support from the IDE.
> Also, namespace fragments are often more generic than function names,
> so more likely to need a custom alias.


That's why I said it was tricky: the language doesn't prevent IDEs 
suggesting different imports; nor does it require you to name namespace 
fragments differently from classes; but that's what happens in practice. 
So to what extent do we build the language based on how it *can* be 
used, and to what extent do we build it based on how it *is* used? What 
if that usage changes over time? What if we add more ways to do it, and 
those aren't used either? I don't think there's an easy answer.


-- 
Rowan Tommins
[IMSoP]

--------------b3mOlOLD6SS0aBuhj3gAH4GY
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 16/06/2024 18:54, Andreas Hennings
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAB-BujZF83_kZYsyWkMAjbowCfSmSaZ7OZebyOG_BNP1S+CGFw@mail.gmail.com">
      <pre>Yes, the possibility for namespace part imports exists.
Unfortunately these namespace imports usually need to be set up
manually, whereas the regular class or function import has better
automatic support from the IDE.
Also, namespace fragments are often more generic than function names,
so more likely to need a custom alias.</pre>
    </blockquote>
    <p><br>
    </p>
    <p>That's why I said it was tricky: the language doesn't prevent
      IDEs suggesting different imports; nor does it require you to name
      namespace fragments differently from classes; but that's what
      happens in practice. So to what extent do we build the language
      based on how it *can* be used, and to what extent do we build it
      based on how it *is* used? What if that usage changes over time?
      What if we add more ways to do it, and those aren't used either? I
      don't think there's an easy answer.</p>
    <p><br>
    </p>
    <pre class="moz-signature" cols="72">-- 
Rowan Tommins
[IMSoP]</pre>
  </body>
</html>

--------------b3mOlOLD6SS0aBuhj3gAH4GY--