>>>>> On Fri, 1 Jun 2001 19:40:30 -0700 (PDT), Tomas Styblo <[EMAIL PROTECTED]> said:
>> Sounds like CGI:: namespace is not perfectly
>> appropriate. I'd expect
>> such a thing in the HTML namespace.
> Well, I chose the CGI:: namespace because the module
> is suited for web applications. I hardly can imagine
> any other way to use it in real world situations. But
> maybe HTML::CgiChecker would be more appropriate.
Well, when it checks HTML, it is HTML::something and should not be
limited to a CGI interface because if a HTML checker limits itself to
a CGI interface it isn't very modular. If, on the other hand, it has
some modular CGI interface constructor, it should not be limited to
HTML checking because if it limits itself in what it is doing, it
isn't very modular. If it has both a modular CGI interface constructor
AND everything to check HTML, it should probably be split into two
modules.
Note, I'm not trying to persuade you to change anything, just to
clarify how name, intent and design fit together.--Thanks!
--
andreas
