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 suggested a
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
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 know
- 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::
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'd
