Front page | perl.perl5.porters |
Postings from January 2022
On 2022-01-25 2:41 a.m., Neil Bowers wrote:
> I like the idea of syntactic support for function libraries, but I don’t like
> the proposed use of the word "module".
>
> We have existing, well-established, terminology where a /module/ is a package in
> a .pm file of the corresponding name, and a module can either be a class /or/ a
> function library (or the love child of both).
>
> I don’t have a great alternative to suggest ("sublibrary", "exporter",
> "library", … ?)
I don't have a problem with the term "module" for this. It works for Raku.
However, I'm also okay with considering some other terms.
The "exporter" one is I feel the best out of what you enumerated, and is very
specific to the main distinctiveness of these.
I oppose using the keyword "library" or any compound based on it, as this is
best kept as a very generic term that covers any kind of Perl package or
collection of such.
Outside those, experience in designing my own Muldis Object Notation / Muldis
Data Language / etc, has shown that a thesaurus is a great help.
Basically, its good to look in a thesaurus for inspiration for many other words
we can pick which don't already have programming language associations and so we
can invent whatever meaning we want.
For example, see all the various synonyms for "package" or "library" or "book"
etc, see one we like and give it the meaning we want.
Otherwise, I'd go with either "module" or "exporter".
-- Darren Duncan
Thread Previous
|
Thread Next