> I don't see how HPL (an HTML templating system) is related to class
> syntax in Perl. Modules should be modular and each do one thing, one
> thing well. This module is widely applicable, including to many non-web
> applications. It seems, to me at least, that Class::HPLOO can be split
> into two fully independent modules (HPL and Class).
Well, this is why I made Class::HPLOO not dependent of HPL source. This is
why the HTML block resource is implemented simplier, and not from HPL (that
I haven't released yet).
Actually HPL contributed with a lot of modules, that I release them
separeted from HPL, soo, other users can use internal resources of HPL in
other projects.
>...
> The following improvement makes it unambiguous:
>
> sub UNDEF { bless {}, "Class::HPLOO::UNDEF" }
>
> followed by
>
> return undef if ref($ret) eq 'Class::HPLOO::UNDEF';
Well, is exactly what I have introduced, but the constant is just UNDEF, and
should be, since Class::HPLOO is not a base class for code, is just the
generator of the code that will run. Need to be in this way, since if I want
to convert my HPLOO code to a normal Perl Module, that isn't dependent of
Class::HPLOO, I just use the BUILD resource of Class::HPLOO, and I will have
a normal PM that works in any standart Perl, and also I ensure that my
releases will avoid Filter::Simple nuances.
>
> Text::Balanced and Filter::Simple indeed have quite a few bugs, which
> means that basically means any module that does source filtering is
> buggy. I emailed five Text::Balanced bug patches with test cases to the
> author over the last two weeks but am still waiting for a response.
> Since Text::Balanced is a core module, distributed with Perl, I'm not
> sure what the best way to report these are. E-mail the author?
> rt.cpan.org? http://rt.perl.org (perlbug)? I prefer the bug tracking
> systems, but both seem barely used for this (e.g.
> http://rt.cpan.org/NoAuth/Bugs.html?Dist=Text-Balanced).
Maybe all of them. For example, I normally receave advice and patches by
e-mail, but RT is a very good tool, but with a little problem, it
doesnt'e-mail the author, soo I wont know if there is a report if I don't
log in the system, what we always forget to do.
> There are also
> problems that can be fixed in Filter::Simple (e.g. FILTER_ONLY
> implementation), which is also a core module, but the rt.cpan.org page
> for it appears dormant as well. -I'm willing to submit patches-, but
> there seems like there should be a more formal patch submission process
> with multiple people able to commit on modules that are core. Anyone
> have any comments?
I think that you should send some e-mail to [EMAIL PROTECTED] They are
alwasy listening and working on Perl.
Best regards,
Graciliano M. P.
