earlier Stas Bekman said:
> > > I`m not sure there is a need for a patch. I think you confuse,
> > > something. When the script is recompiled all the variables belonging
> > > to the package decalared by Apache::Registry or similar are getting
> > > reset. If you require/use() some modules that declare packages and have global
> > > variables -- these won`t be reset unless reloaded or initialized in your code.
> >
> --snip--
>
then later:
> Now once this package is built and compiled, *nothing* happens to it --
> it's like a loaded from the file module. If you don't initialize vars at
> the beginning of your script. And no, Apache::Registry doesn't reset the
> global vars.
ah. that's what I thought. but previously you said "all the variables belonging to
the packaged decalared by Apache::Registry or similar are getting reset." that is the
point i was arguing, but it looks like we both agree. perhaps you meant to say "all
the lexicals belonging to the file loaded by Apache::Registry or similar are getting
reset".
back to the original posting that started this thread, the poster was unaware that the
package variables would not be reset when the file containing that package was
recompiled. we both agree that they will not be reset. he did not think that this
fact was clear in the guide.
--
___cliff [EMAIL PROTECTED]http://www.genwax.com/
