Ian Langworth writes:
> Ovid: TAP::Parser::Pedantic
>
> Schwern: TAP::Parser::Heuristic
That's the best idea: nobody claiming that his particular parser is
_the_ TAP::Parser (or even _the_ TAPx::Parser), but giving them parallel
names with adjectives that hint at ways in which they differ. Even
Ovid wrote:
- Original Message
From: Nik Clayton <[EMAIL PROTECTED]>
Ovid wrote:
I'm perfectly comfortable with this idea, but what I'm trying to figure
> > out then, is the namespace for my parser. It's a TAP parser, after all.
> > Any suggestions? I see that Adam has suggeste
Ovid: TAP::Parser::Pedantic
Schwern: TAP::Parser::Heuristic
I've always feared /^[A-Z]+x::/ namespaces because I never understood
them. For the longest time, I thought Jesse was working on "DBI
eXtreme" with SearchBuilder and whatnot.
On 7/8/06, Ovid <[EMAIL PROTECTED]> wrote:
I'm perfectly co
On Sat, Jul 08, 2006 at 05:10:50AM -0700, Ovid wrote:
> - Original Message
> > From: Nik Clayton <[EMAIL PROTECTED]>
> > TAPxParser
>
>
> Thought about that, but immediately discarded it. TAPx::OVID::Parser doesn't
> say anything about the parser other than authorship and the latt
- Original Message
> From: Nik Clayton <[EMAIL PROTECTED]>
> Ovid wrote:
> > I'm perfectly comfortable with this idea, but what I'm trying to figure
> > out then, is the namespace for my parser. It's a TAP parser, after all.
> > Any suggestions? I see that Adam has suggested a TAPx::
Ovid wrote:
I'm perfectly comfortable with this idea, but what I'm trying to figure
> out then, is the namespace for my parser. It's a TAP parser, after all.
> Any suggestions? I see that Adam has suggested a TAPx:: namespace,
> but there could still be competing TAPx::Parser modules. Don't kn
I'm perfectly comfortable with this idea, but what I'm trying to figure out
then, is the namespace for my parser. It's a TAP parser, after all. Any
suggestions? I see that Adam has suggested a TAPx:: namespace, but there could
still be competing TAPx::Parser modules. Don't know if that would
I propose that we all avoid grabbing the juicy names in the top level
TAP namespace, such as TAP::Grammar, TAP::Parser and so on. This
avoids one module getting the special status of being "the"
TAP::Parser. AKA "The CGI.pm problem". Sort of declare a namespace
Antarctic Treaty.
For example, I
