> On Jul 4, 2024, at 12:02 PM, Mike Schinkel <m...@newclarity.net> wrote:
>
> Your definitions are language-specific. For example, in Go the definitions
> for those terms are the opposite of how you defined them.
>
> The point being that PHP is free to choose how they are defined with respect
> to PHP.
>
> To which I will add "as long as the terms are used consistently.”
Okay, some languages may swap the terms, others like JS glom the concepts
together, and in Perl 5 “package Foo” defines a module. I’d say most PHP devs
are more familiar with the terms as they’re used in JS, but whatever makes
sense for PHP is what’s best. I suppose I do have a dog in the fight, but I
don’t much care how it’s groomed.
Then there’s GHC Haskell which has `import “package-name”
ModuleName.{Foo,Bar,Baz}`, which seems to cover all the bases. Decent ideas
from the syntax, but I don’t think I want to replicate backpack :)
—c
