Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123639
Feedback-ID: id5114917:Fastmail
Content-Type: multipart/alternative;
 boundary="------------SD2AZiY0lvGqARj0vTXtVFHw"
Message-ID: <4e439377-5c20-40d7-bb99-5d0ac6c348e9@rwec.co.uk>
Date: Sun, 16 Jun 2024 18:08:46 +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>
Content-Language: en-GB
In-Reply-To: <CAB-BujYmFxyNQV0-PZYz72A8CUHnkVvuHwPBvtOiBO9vV7+uDQ@mail.gmail.com>
From: imsop.php@rwec.co.uk ("Rowan Tommins [IMSoP]")

This is a multi-part message in MIME format.
--------------SD2AZiY0lvGqARj0vTXtVFHw
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

On 16/06/2024 16:24, Andreas Hennings wrote:
> For a function call, the namespace is usually only visible in the
> imports list at the top of the file.

This is one of those interesting cases where the language itself is 
flexible, but people are used to a specific style: a use statement can 
import any level of namespace, to provide as much or as little context 
as needed in a particular piece of code.

namespace Acme\Artistry\Color {
     function fromRgb($red, $green, $blue) { /*...*/ }
}

namespace My\Own\Application {
     use Acme\Artistry\Color;

     // ...
     $color = Color\fromRgb(1,2,3);
     // ...
}


Maybe that's rare in practice, but it's always tricky to judge how much 
the language should account for such habits  - see also "every class 
needs a new file", and my pet hate "deprecation notices get promoted to 
errors".


> The class name that is part of a static method call hints at an object
> type, whereas for a namespace fragment it may not be really clear what
> it describes.
> In a static factory call, like `Color::fromRgb($red, $green, $blue)`,
> I would argue that having the class name as part of the call improves
> DX.

This example seems slightly off: if the static method is on the class it 
is a factory for, that class clearly isn't completely static.

Presumably what we're actually talking about is something like 
"ColorFactory::fromRgb(...)" - or maybe 
"GraphicsFactory::colorFromRgb(...)", where you might well want to 
abbreviate to "colorFromRgb(...)".


Your points are generally well made, I just wanted to point out there 
are some nuances in that particular area.

Regards,

-- 
Rowan Tommins
[IMSoP]

--------------SD2AZiY0lvGqARj0vTXtVFHw
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!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 16:24, Andreas Hennings
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAB-BujYmFxyNQV0-PZYz72A8CUHnkVvuHwPBvtOiBO9vV7+uDQ@mail.gmail.com">
      <pre>For a function call, the namespace is usually only visible in the
imports list at the top of the file.</pre>
    </blockquote>
    <br>
    <p>This is one of those interesting cases where the language itself
      is flexible, but people are used to a specific style: a use
      statement can import any level of namespace, to provide as much or
      as little context as needed in a particular piece of code.</p>
    <p>namespace Acme\Artistry\Color {<br>
          function fromRgb($red, $green, $blue) { /*...*/ }<br>
      }<br>
      <br>
      namespace My\Own\Application {<br>
          use Acme\Artistry\Color;<br>
      <br>
          // ...<br>
          $color = Color\fromRgb(1,2,3);<br>
          // ...<br>
      }</p>
    <p></p>
    <p><br>
    </p>
    <p>Maybe that's rare in practice, but it's always tricky to judge
      how much the language should account for such habits  - see also
      "every class needs a new file", and my pet hate "deprecation
      notices get promoted to errors".<br>
    </p>
    <p><br>
    </p>
    <blockquote type="cite"
cite="mid:CAB-BujYmFxyNQV0-PZYz72A8CUHnkVvuHwPBvtOiBO9vV7+uDQ@mail.gmail.com">
      <pre>
The class name that is part of a static method call hints at an object
type, whereas for a namespace fragment it may not be really clear what
it describes.
In a static factory call, like `Color::fromRgb($red, $green, $blue)`,
I would argue that having the class name as part of the call improves
DX.</pre>
    </blockquote>
    <br>
    <p>This example seems slightly off: if the static method is on the
      class it is a factory for, that class clearly isn't completely
      static.<br>
    </p>
    <p>Presumably what we're actually talking about is something like
      "ColorFactory::fromRgb(...)" - or maybe
      "GraphicsFactory::colorFromRgb(...)", where you might well want to
      abbreviate to "colorFromRgb(...)".</p>
    <p><br>
    </p>
    <p>Your points are generally well made, I just wanted to point out
      there are some nuances in that particular area.<br>
    </p>
    <p>Regards,<br>
    </p>
    <pre class="moz-signature" cols="72">-- 
Rowan Tommins
[IMSoP]</pre>
  </body>
</html>

--------------SD2AZiY0lvGqARj0vTXtVFHw--