On Tuesday, July 2, 2002, at 01:25 AM, Brian Ingerson wrote: > Hi Ken, > > I think you're best off to use one directory per .pm. I'd like > to see why > this would be a pain. You'd pretty much need to do the same > thing in XS.
XS isn't typically a good benchmark for programmer convenience. ;-) It would be a pain because my working directories would no longer mirror the structure of my code. It would also be a pain to maintain many separate Makefile.PLs instead of just one centralized one. > Of course, if you can convince me of a better way I'll do it for you :) What an offer. =) The way I'd like to see it work is that I could have all my modules in a lib/ directory, the same way I'd usually have them if I weren't using Inline. Then, in each .pm file I used Inline for, I'd just put the correct 'use Inline' statements into the modules. This would make Inline act like other Perl module dependencies - currently, if I decide I want to use DBI in a module, that choice doesn't require me to separate all such .pm files into their own directories. Of course, I haven't suggested an implementation for this. To do so, I'd need to know more than I do about how Inline manages to compile everything and get it into blib/ . I'll probably know that before too long, but I don't know much yet. -Ken
