On Sat, Nov 15, 2003 at 02:51:26PM +1100, Andrew Savige wrote: > Michael G Schwern wrote: > > I use t/lib so the top level t/ directory doesn't get cluttered (and for > > compatibility with the Perl core which may be important later for A::T). > > Yes, I like that. Should I call it: > t/lib/Test/Archive/Tar... > or: > t/lib/Archive/Tar/Test... > or something else?
It'll never get installed so it doesn't matter. The only real concern is that the name doesn't clash with another module that Archive::Tar might use. Don't drive yourself nuts over it, its only for AT internal use so the naming isn't that important. You'll noticed ExtUtils::MakeMaker uses MakeMaker::Test instead of ExtUtils::MakeMaker::Test because I didn't want to type as much. I might have even gone with MM::Test. t/lib/AT/Test would be fine. You can always change it later if there's a problem. > I took a quick look a mod_perl and Template Toolkit (TT). > TT has a: > lib/Template/Test.pm > which looks wrong to me (should that not be under t/lib instead?). *shrug* Maybe they want it to be installed. Maybe its useful for people testing programs that use TT. Maybe they didn't think of t/lib. Its at least a fully formed module with docs and all rather than just a little test utility thing or bit of dummy data. > Not sure, but mod_perl seems to have unbundled the test suite > into a separate Apache-Test distribution. Again, why should > that be called Apache-Test rather than Test-Apache? Apache::Test was originally bundled with mod_perl (still is) but was recently dual-lifed as a stand-alone dist. Because everything else in mod_perl is in the Apache:: namespace they probably figured it made sense to call it Apache::Test instead of Test::Apache. That's what I figure. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/ Playstation? Of course Perl runs on Playstation. -- Jarkko Hietaniemi
