On Apr 25, 2007, at 2:22 AM, Fausto Lelli wrote: > The new module could be War::Configuration::API as a place to store > 'public methods', and maybe a War::Configuration::Internal to store > what we > have now. I'm not proposing to 'forbid' War::Configuration::Internal, > only it must be used with some cautions. > > What do you think?
What configuration options are you trying to hide from users? Just glancing through, I don't see any real reason to try to hide anything. I don't think this project is so big that it warrants the extra level of indirection. Maybe it's a cultural thing, but as a Rubyist, I expect to be allowed to shoot off my own foot. Why not just expose the Configuration like Jon has suggested, and only document the options you want people to change? :dudley _______________________________________________ Jruby-extras-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/jruby-extras-devel
