in reply to Registering Subclass Modules via Plugin

I think a factory is for when the caller knows what they want. Your case is different.

I find out which subclasses are available by scanning all or part of the @INC path list for modules in a given namespace. I do this once, as the app starts. Note that big @INC scans can be time prohibitive. In that case, I look to see which directory my parent module lives in by checking %INC, then look there for my children, making the big assumption that they get installed to the same place as the parent. It works for Bigtop's tentmaker.


The Gantry Web Framework Book is now available.
  • Comment on Re: Registering Subclass Modules via Plugin

Replies are listed 'Best First'.
Re^2: Registering Subclass Modules via Plugin
by 2xlp (Sexton) on Nov 14, 2007 at 20:11 UTC
    Thanks Phil- thats exactly what I want to be doing, and an assumption that I'm 100% ok with making.

    I just went though Tentmaker, and pulled some ideas. Unfortunately you're using File::Find so I can't do the same-thing (i wish though!). This is for an app running under mod_perl, and File::Find is a PITA when it comes to memory on that platform.