On 30/03/03 11:34 +0200, Arthur Bergman wrote:
>
> On söndag, mar 30, 2003, at 00:52 Europe/Stockholm, Perl Authors Upload
> Server wrote:
>
> >
> > Module::Include allows you to upstream duplication in Perl
> > projects. It stores code both inline (between #include and #end
> > statements) and in a repository module that is a subclass of
> > Module::Include.
> >
> > In addition you can pass arguments to #include that get used in a
> > templating system. And you can override the default templating to
> > use any other template system.
> >
> > Module::Inlude rewrites your code and also rewrites the subclass
> > repository. It comments out the 'use Subclass' line from your code
> > so that when you ship your code, the receiver does not need to have
> > Module::Include.
> >
>
> Is Module:: really a good name for this since it's actually a kind of
> macro language?
It's intended to be a module authoring tool. A way to upstream duplicate
or similar module parts that can't be put into subroutines. Like the
copyright section of pod, or code that is comon across an authors
distributions.
It is also a namespace for other module building include templates like:
Module::Include::README
Module::Include::Changes
Module::Include::OOStuff
It is also meant to complement the new wave of Module::* tools.
So I think the name is exactly what it should be.
Cheers, Brian
