In 2.0.0, if there are heirarchical packages, and Apache2::Reload is
configured to reload the 'parent', it blows away the 'children' package
namespaces (and doesn't reload the children.) For example, if @INC has:
Fubar.pm
Fubar/Child.pm
And Apache2::Reload reloads package Fubar, it blows away
F
Mark wrote:
In 2.0.0, if there are heirarchical packages, and Apache2::Reload is
configured to reload the 'parent', it blows away the 'children' package
namespaces (and doesn't reload the children.) For example, if @INC has:
Fubar.pm
Fubar/Child.pm
And Apache2::Reload reloads package Fubar, it
Hello Mark,
I have the same problem as well, though I don't have a decent solution/
workaround for it. All I ended up doing was to use the subpackages. And
when the subpackage changes, I touch the main package as well. That
seems to cause Apache to reload.
Mark wrote:
In 2.0.0, if there ar
Mark wrote:
> Mark wrote:
>
>> In 2.0.0, if there are heirarchical packages, and Apache2::Reload is
>> configured to reload the 'parent', it blows away the 'children' package
>> namespaces (and doesn't reload the children.) For example, if @INC has:
>>
>> Fubar.pm
>> Fubar/Child.pm
>>
>> And Apach
Philippe M. Chiasson wrote:
Mark wrote:
Mark wrote:
In 2.0.0, if there are heirarchical packages, and Apache2::Reload is
configured to reload the 'parent', it blows away the 'children' package
namespaces (and doesn't reload the children.) For example, if @INC has:
Fubar.pm
Fubar/Child.pm
