Hi,

I have a little issue with the implementation of the navigator. In case
that the user does provide its own NavigatorEngine, the lifetime
management is disturbed. In that case the user's client code is
responsible for creation of the object but the Navigator class does
actually perform the deletion of the object. Since this typically
happens in a different runtime context (exe, dll) their are possibly
different memory handler performing the actual task. This would be a
problem.

Is it possible to handle the NavigatorEngine objects by boost shared
pointers inside the Navigator, which (imho) do not show this problem?
Another possibility would be to not manage the lifetime of the user
defined NavigatorEngine objects but leave it in the client code.

Best,
Johannes





____________
Virus checked by G DATA AntiVirusKit
Version: AVF 19.541 from 20.09.2009
Virus news: www.antiviruslab.com

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to