On 11 Oct 2001, Andreas J. Koenig wrote:
> > On Mon, 8 Oct 2001 09:47:07 -0600 (MDT), <[EMAIL PROTECTED]> said:
>
> >> I have the impression you're taking a namespace for a function.
> >> Wouldn't it be more logical to have a class HTML::DataConvert or some
> >> such and have mthods in the
> On Mon, 8 Oct 2001 09:47:07 -0600 (MDT), <[EMAIL PROTECTED]> said:
>> I have the impression you're taking a namespace for a function.
>> Wouldn't it be more logical to have a class HTML::DataConvert or some
>> such and have mthods in there that accomplish all related tasks.
>>
>> Ther
In perl.modules, you wrote:
>
>> I have the impression you're taking a namespace for a function.
>> Wouldn't it be more logical to have a class HTML::DataConvert or some
>> such and have mthods in there that accomplish all related tasks.
>>
>> There's certainly more than one possible name for such
> I have the impression you're taking a namespace for a function.
> Wouldn't it be more logical to have a class HTML::DataConvert or some
> such and have mthods in there that accomplish all related tasks.
>
> There's certainly more than one possible name for such a class, but
> HTML::DataConvert
> On Tue, 2 Oct 2001 02:41:31 +0200, "Perl Authors Upload Server"
><[EMAIL PROTECTED]> said:
> The following module was proposed for inclusion in the Module List:
> modid: Data::html2results
> DSLIP: adpOp
> description: Parses arbitrary html to an array of arrays
Hi, and thanks for mailing [EMAIL PROTECTED] This is an automated
response to your email.
We get lots of mail, and sometimes it takes us a while to get to yours.
Please be patient, we *will* try and respond as soon as we can gather
enough tuits.
In the meantime, here are some pointers which ma
