> > Yes and no. If XS libraries are written with OO-style wrappers (which, IMHO, > they always should be), then surely you can catch the unloading in a DESTROY > sub and use that to do the deallocation of resources? Perl can only manage > Perl resources, and extension resources should be the responsibility of the > the programmer. > That's why Doug wrote we need the perl_destruct/perl_free addtionaly to the dlclose. These two routines will take care of the Perlpart destruction, i.e. call the DESTROYs GErald
- Re: horrible memory consumptio... Stas Bekman
- Re: horrible memory consumptio... Bill
- Re: horrible memory consumptio... Cliff Rayman
- Re: horrible memory consumptio... Vivek Khera
- Re: horrible memory consumptio... Doug MacEachern
- Re: Why does Apache do this braind... Daniel Jacobowitz
- Re: Why does Apache do this br... Alan Burlison
- Re: Why does Apache do this braind... Jens-Uwe Mager
- RE: Why does Apache do this braindamaged dlclose/dlopen ... Gerald Richter
- RE: Why does Apache do this braindamaged dlclose/dlopen ... Stephen Anderson
- RE: Why does Apache do this braindamaged dlclose/dl... Gerald Richter
- RE: Why does Apache do this braindamaged dlclose/dlopen ... Stephen Anderson