Stas Bekman wrote:
Harry Danilevsky wrote:
I did send the patch to Matt couple of days ago, but haven't heard
back yet.
Matt is on vacation
I suppose I can also brace myslef, add namespaces, and clean up my own
code.
That's a good idea.
As for the versioning, if this patch could be
[...]
Anyway, I decided to add another directive to Apache::Reload
PerlSetVar ReloadDirectories /site/lib /usr/local/apache/conf
Apache::Reload allows you to define which modules to reload using the
patterns like so:
PerlSetVar ReloadAll Off
PerlSetVar ReloadModules Apache::* My::*
Is
Two reasons :
1. My site-specific modules don't necessarily have a common namespace
(or even several namespaces);
they just all live in /site/lib. Without a ReloadDirectories-like filter
every time I add another module,
say, /site/lib/Reports.pm I'll need to add Reports to ReloadModules, and
Harry Danilevsky wrote:
Two reasons :
1. My site-specific modules don't necessarily have a common namespace
(or even several namespaces);
they just all live in /site/lib. Without a ReloadDirectories-like filter
every time I add another module,
say, /site/lib/Reports.pm I'll need to add
I certainly agree with attaching a common prefix to a library, but what
if I am already dealing
with a bunch of modules written without prefix, and enough application
code using those packages ?
I suppose I could change the code, or alias names in symbol table, or do
some other trick;
I just
