On 24 Mar 2002 at 20:56, Matt Sergeant wrote:
> I've been desperately trying to debug why TaglibHelper XSP taglibs need
> you to define the parse_start, parse_end and parse_chars subs. And I can't
> for the life of me figure it out.
>
If you are using AxKit::XSP::SAXHandler, the parse_start and
parse_end methods in TalibHelper shed some light on the problem:
my $pkg = caller;
# horrible hack: if the caller is the SAX library directly,
# then we'll just have to assume that we're testing TaglibHelper
$pkg = "Apache::AxKit::Language::XSP::TaglibHelper" if $pkg eq
"AxKit::XSP::SAXHandler";
I don't know what a good solution would be, perhaps somehting
like:
TaglibHelper needs to know which package to look in to get the
@EXPORT_TAGLIB information.
Daemmon Hughes
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
