On Wed, 09 Jul 2008, Javier wrote: Hi Javier,
> I think that INIT/EXIT procedures is fine controlled by runner so only > not registering them in globally solves the thing but it's possible that > I lose something more: now hrb module is CG. They have to be registered or some important functionality will be broken. But of course it's possible to block executing EXIT procedures only for .hrb modules. Anyhow it does not resolve the problem. The question is: when EXIT procedures should be executed. Now they are executed at the beginning of HVM quit procedure before any subsystems are unloaded. If we make such modification then they will be executed when variable will be out of scope. It means that some important HVM parts may be deactivated, f.e. RDD will be unloaded so EXIT procedure will not be able to write any data to DBFs. I would like to keep current execution of EXIT procedures and I can easy block any other EXIT procedures to protect against double execution. But I would like also to execute EXIT procedures for modules loaded and unloaded during HVM quit. This needs some deeper modifications. Anyhow maybe it will be better and more clear to simply block loading new .hrb modules when HVM QUIT procedure started what fully eliminates the problem. best regards, Przemek _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
