----- Original Message ---- > From: Steffen Schwigon <s...@renormalist.net> > Hi! > > [TAP Namespace Nonproliferation Treaty] > > Should I name a module that represents the result of a TAP parse as > data structure > > TAP::Data > > or > > TAPx::Data > > before I upload to CPAN? > > There are no TAPx:: modules there except the intermediate TAPx::Parser > which is now TAP::Parser. But there are some TAP:: modules. That's why > I ask.
I've no problem with you using the TAP:: namespace. For things like, say, DBIx, we're talking about a particular namespace that the author (Tim Bunce) has every right to reserve. In this case, we have a protocol, TAP, and a namespace, TAP::. Now that things have settled down and TAPx::Parser won the testing wars, I'm quite happy to be magnanimous and say "we don't own the protocol name" :) What I do have a problem with is "::Data". I would like to seething more descriptive. "DATA" is usually a problematic name since *everything* is data in the end. Cheers, Ovid -- Buy the book - http://www.oreilly.com/catalog/perlhks/ Tech blog - http://use.perl.org/~Ovid/journal/ Twitter - http://twitter.com/OvidPerl Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
