in reply to RFC: Wider scope for HTML::TokeParser::Simple

Why?

Honestly why?

Ok, forget that for a second, do you have any clue as to what kind of a user base you've got (or rather your module -- how many people use it)?

In the very least I think you should either do like the HTML::Parser folk did, and make with a

HTML::TokeParser::Simple->new ( api_version => 3 );
or just go with a namespace change HTML::TokeParser::Simpler. This really depends on if you're going to put in the work to keep the old style api, or just changing things around completely (even if its mostly cosmetic).

Other than that I only have a question, are you going to go with AUTOLOAD now?

Replies are listed 'Best First'.
Re: Re: RFC: Wider scope for HTML::TokeParser::Simple
by Ovid (Cardinal) on Jul 10, 2002 at 21:00 UTC

    First, the AUTOLOAD has been gone ever since I released the first version. That's not an issue (of course, if the module works as advertised, I don't think that leaving the AUTOLOAD in would have been that much of an issue, either, but I digress...)

    podmaster wrote: "Why? Honestly why?"

    Ovid responds: "why what?" I raised several issues there. Which one are you asking about? I think you're talking about the interface change, but rather answer a question you may not be asking, I'll just ask you to clarify your question :)

    Cheers,
    Ovid

    Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.

      Why are you expanding the scope?

      I can understand the is_tag addition, but why add all that HTML::Tagset stuff? ( it wouldn't be simple no more )

      I know the AUTOLOAD has been gone, but with the numerous tags, would it be insane not to go with it (if you add that is_head is_body stuff)? Also, who's to say what's a valid tag , ie, what subset of html are you going to support (don't say whatever HTML::Tagset supports ;)?

      Seeing as i'm the only who's got anything to say, I say knock yourself out, but please keep in mind my previous comments on the interface (api version v. namespace change).