--- Luke Closs <[EMAIL PROTECTED]> wrote: > On 2/22/07, Ovid <[EMAIL PROTECTED]> wrote: > > > > Telling me "you can only use t/lib for mocked modules" > > > Woah, dude. mocked.pm loads mocked modules from t/lib. You can use > t/lib > for whatever else you want. > > So you could keep your existing test modules there, and put the mock > test > modules there too.
OK, I take your point. I just have a personal preference for using separate paths for separate types of modules. So right now, if I see something in t/lib/, I know that it's a helper module for tests. I would be tempted, were I creating multiple mocked modules, to create a t/mocked/ directory, since I think code organization gets very important as a codebase grows larger. Still, t/lib doesn't seem like too bad of an idea :) Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/
