Re: Please review new Perl 5 Module List
Martijn Koster (m.koster@nexor.co.uk)
Mon, 27 Feb 1995 07:49:23 +0000
> > Arguably that should be WWW::CGI, but let's leave that until at least
> > the protocols make sense.
> >
> I see a need for many CGI related modules so I'm happy to see CGI::* used.
> Not that I have any real influence :-)
Hmm, you don't want to pollute the toplevel namespace too much... We
need to allow future the Common Graphics Interchange modules and the
Cool Goodies and Ideas module ? :-)
> I'm wary of slapping a WWW:: prefix on everything. It would be easy to argue
> that WWW::HTTP should actually be Net::HTTP for example.
Yes, that's where I had it before seeing the WWW section :-) The thing
about libwww-perl is that it provides a WWW frontend (formats
everything into HTL, and makes it look like a HTTP request); so
WWW::Gopher will behave like a Web server, whereas Net::Gopher
probably doesn't.
So I think in that case the WWW:: prefix is probably justified.
> In general I'd like to see more small well focused modules with 'narrow'
> names which accurately reflect the functionality of the module. (This
> applies to all modules, not just WWW ones.)
Agreed.
> WWW::Log and WWW::Robots have much narrower functionality, based on their
> descriptions, than their names would suggest (to me anyway). If they are
> only intended for parsing I'd add Parse to the name. If they are intended
> to be a home for more general Log and Robot functionality I'd remove Parse
> from the description.
Hey, they're only 'i's, don't knwo what they might do yet :-)
> > If so we can get back to talking design :-)
> >
> Yippie. I wish more people would!
We'll keep you posted...
-- Martijn
__________
Internet: m.koster@nexor.co.uk
X-400: C=GB; A= ; P=Nexor; O=Nexor; S=koster; I=M
X-500: c=GB@o=NEXOR Ltd@cn=Martijn Koster
WWW: http://web.nexor.co.uk/mak/mak.html