On Wed, Mar 25, 2009 at 10:25 AM, Jonathan Yu <jonathan.i...@gmail.com> wrote:
> Class::ForSystem, since it's not too long and conveys what the module > is designed to do. I'm for Class::ForSystem or Class::ForOS, with the magically included per-OS packages being under the proposed module, such as Class::ForOS::linux::File::Tail which is what Class::ForOS would load the replacements out of, were Class::ForOS used in File::Tail where $^O eq 'linux'. Class::PerOS is also appealing instead of Class::ForOS. How does it interact with AUTOLOAD? Does it matter if it is used at the top or bottom of the module, or in the middle? Is there a possibility of other systems of alternatives that key on something other than $^O (such as the ever-popular "use less ..." family of imaginary modules, for declaring optimization priorities, which now appears on CPAN, as documentation only) playing nice with Class::PerOS, by providing hooks? Class::Alternatives could be a framework for frameworks of providing alternatives, of which Class::PerOS would be the first demonstration Good coffee today, I guess :) -- "I lived in Hannibal fifteen and a half years, altogether, then ran away, according to the custom of persons who are intending to become celebrated." -- Samuel Clemens
