Conrad, Bill (ThomasTech) <> wrote: > The reason I wanted to destroy the eval was that there are certain > default sub-routines the plugin might have. If the plugin has them I > want to execute them rather then the default logic contained within > the editor.
In that case your plugin base class would contain all of the default logic, and your derived, schema specific plugin classes would override the base class logic as appropriate. This is fairly basic OO, in case it wasn't obvious. > If the user closes a file and opens a different one I > don't want plugin logic associated with the old file executed against > the new file. If the plugin object is associated with the file being edited (i.e. the plugin logic for a file is executed by calling member functions of its plugin object), then it would be created when the file is loaded, and destroyed when the file is closed. Also, as I said before, by associating the plugin object with the file being edited, it means that, other design constraints permitting, multiple files can be edited at the same time. > Also, any memory allocated by the plugin is no longer > needed when the file is closed. Any memory allocated by the plugin object will be released when it is destroyed. However, in case you thought otherwise, this memory is only released for the program to re-use, it is not normally released to the operating system until the program terminates. HTH -- Brian Raven ================================= Atos Euronext Market Solutions Disclaimer ================================= The information contained in this e-mail is confidential and solely for the intended addressee(s). Unauthorised reproduction, disclosure, modification, and/or distribution of this email may be unlawful. If you have received this email in error, please notify the sender immediately and delete it from your system. The views expressed in this message do not necessarily reflect those of Atos Euronext Market Solutions. L'information contenue dans cet e-mail est confidentielle et uniquement destinee a la (aux) personnes a laquelle (auxquelle(s)) elle est adressee. Toute copie, publication ou diffusion de cet email est interdite. Si cet e-mail vous parvient par erreur, nous vous prions de bien vouloir prevenir l'expediteur immediatement et d'effacer le e-mail et annexes jointes de votre systeme. Le contenu de ce message electronique ne represente pas necessairement la position ou le point de vue d'Atos Euronext Market Solutions. _______________________________________________ ActivePerl mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
