que?

-- 
ask bjoern hansen - <http://www.netcetera.dk/~ask/>
more than 70M impressions per day, <http://valueclick.com>

---------- Forwarded message ----------
Date: Mon, 6 Nov 2000 13:42:40 -0800 (PST)
From: Paul J. Lucas <[EMAIL PROTECTED]>
To: Sean M. Burke <[EMAIL PROTECTED]>
Cc: Nick Chirca <[EMAIL PROTECTED]>, [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: HTTP::Request::Form and TreeBuilder.pm

On Mon, 6 Nov 2000, Sean M. Burke wrote:

> Paul Lucas: you should to rename your dist to something other than HTML_Tree
> / HTML::Tree.

        Unfortunately, there is no better name.

> You named it that without consideration of the fact that there was already a
> dist called HTML-Tree.

        First, unless you can read my mind, you have no knowledge of
        what I considered and what I didn't.  Second, I /did/ consider
        it, but decided to do what I did.

> And many people

        Actually, no more than two before you.

> have since /patiently/ pointed out that HTML_Tree/HTML::Tree is a confusing
> name; and apparently it /is/ actually confusing people.

        There's a massive amount of confusion in thw world.  Renaming
        my module something else will not reduce that confusion by any
        significant amount.

        Additionally, I've also /patiently/ pointed out that my
        software is, first and foremost, a C++ library.  In /that/
        namespace, my chosen name is sufficiently unique.  And, again,
        said library just so happens to have a Perl language binding
        thrown in for free.

        A single developer isn't going to use both my package /and/
        somebody else's simultaneously anyway.

> I don't care if you publish your module dist under some other name, but just
> stop publishing in CPAN under the name HTML::Tree or HTML_Tree.

        When I submitted the module, the module-powers-that-be could
        have rejected it: they didn't.

        There simply aren't enough synonyms in English that accurately
        describe what my module does.  Therefore, the only resort would
        be to contrive a name that has nothing to do with what the
        module does.  (For instance HTML::Mason is a bad name.  Can you
        tell what that does from the name?  I can't.)  I don't want to
        pick a meaningless name just so it's unique.  Sorry.

        - Paul

Reply via email to