It's been a while since I finished dealing with that, but I recall that my python components suddenly became rather prone to crash if I didn't explicitly "nullify" a series of references to UNO objects that (to my knowledge) should be garbage-collected. :o) I guess you might retrieve most of the issues I faced by looking up the issue base for user pelizzon in the first half of 2006.
Cheers, Jorge. Stephan Bergmann escreveu: > Jorge Marques Pelizzoni wrote: >> Thing is: once I developed a UNO package that worked fine for version >> 1.5 >> but would crash 2.0. So it seems to me that OOo version numbers may come >> handy for installers/updaters. > > In theory, it should not happen that a well-behaved UNO application or > component fails with later OOo versions. (So much for theory.) Out of > curiosity, do you have a quick summary of what made it fail for you? > > -Stephan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > Jorge M. Pelizzoni ICMC - Universidade de São Paulo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
