Commenting out of complete ignorance regarding the actual problem,
but: I've never liked this kind of pattern, because it is hard to
discover and easy to forget.
Is there a better way of handling life cycle stages? I would expect
this kind of method to be always there, possibly with empty
implementations.
Greetings,
Axel
On Oct 20, 2009, at 14:39 , Paul Webster wrote:
If code creates a creates a context with EclipseContextFactory then
they should dispose it when they're done with it. i.e. in our
model/renderer code we have to create and dispose the context. We use
the pattern with IDisposable (as you found :-)
if (context implements IDisposable) {
((IDisposable)context).dispose();
}
PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
e4-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/e4-dev
--
[email protected]
http://www.pst.ifi.lmu.de/~rauschma/
_______________________________________________
e4-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/e4-dev
