Jose, We can not safely unload OLE until AFTER *all* prg code has been executed. This means AFTER the last GC process is completed, so that all PRG destructors have been executed. Otherwise we are causing new bugs, in attempt to protect against buggy 3rd party code.
Ron On Apr 14, 2008, at 6:15 AM, Ron Pinkas wrote: > Jose, > > But Some classes may have DESTRUCTORs that still need OLE. > > Ron > > On Apr 14, 2008, at 6:13 AM, Jose F. Gimenez wrote: > >> Ron, >> >>> What about just AFTER releasing STATICs, before hb_errExit()? >> >> IMO, OLE connections should be totally closed before releasing any >> variable or memory block, but after exit and registered procedures >> execute, to allow them to call any OLE component. That's why I >> suggested that point. >> >> >> Regards, >> >> Jose F. Gimenez >> > > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save > $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http:// > java.sun.com/javaone > _______________________________________________ > xHarbour-developers mailing list > xHarbour-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xharbour-developers > ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ xHarbour-developers mailing list xHarbour-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xharbour-developers
