>> anyway, the code is meant to be more of an illustration than a module you >> would want to use in production, but still... > > > And it suffers from a pretty terrible dependency on the internal structure > of the module you are peeking at to be static. You are basically defining > a copy of the internal configuration structure of a module and can't ever > be guaranteed that it will remain the same.
indeed. and we mention all of these in the text :) > > But, I have to admit to having done exactly just that at least once in > a production environment, so... it is inedeed just another way to do it. and we all know how often httpd changes internal structures, especially in 1.3 ;) > >> and bonus karma points to anyone who groks the latin phrase on page >> 299 ;) > > > ill got, ill spent ;-) :) one translation had it as more of an idiom, meaning "nothing good can come of this," which was my indended meaning. --Geoff -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
