This will mean that when upgrading PEAR, fatal errors will always occur if any major changes are made in lazy-loaded files, because the newer file is included. >For instance, downgrading to 1.3.5 from 1.4.0 destroys the installation without the non-lazy loading.
Hence, if ($package == 'PEAR') lazy load all files before upgrading?
- it's looks alot like an edge case scenario that's affecting more general usage, and maybe a contributor to pearweb load issues?, It seems like it might be worth investigating to try and solve this?
Regards
Alan
Greg Beaver wrote:
Alan Knowles wrote:
Just looking through some of the code, assuming the numbers you gave are
correct, I suspect looking at lazy loading of alot of the classes when
they are needed, rather than bulk loading at the top of each file may
help alot..
Regards
Alan
Greg