From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 Path: backlog3.nntp.dca3.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!newspeer1.nac.net!newsfeed1.swip.net!aioe.org!.POSTED!not-for-mail From: Victor Porton Newsgroups: comp.lang.ada Subject: Re: Library cleanup Date: Tue, 20 May 2014 20:27:20 +0300 Organization: Aioe.org NNTP Server Message-ID: References: <1vqik1odcvjrw$.tsdp6cr7bp5y.dlg@40tude.net> NNTP-Posting-Host: LRua1LhEwYx/r1KnMXeYtA.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: abuse@aioe.org User-Agent: KNode/4.12.4 X-Notice: Filtered by postfilter v. 0.8.2 Xref: number.nntp.dca.giganews.com comp.lang.ada:186515 Date: 2014-05-20T20:27:20+03:00 List-Id: Dmitry A. Kazakov wrote: > On Tue, 20 May 2014 15:56:40 +0300, Victor Porton wrote: > >> I am writing bindings for a C library which requires both initialization >> and cleanup: >> >> [[[ >> raptor_init() >> raptor_finish() >> >> Initialise and cleanup the library. These must be called before any >> raptor class such as raptor_parser, raptor_uri is created or used. Note: >> as of 1.4.19 these are wrappers around a static instance of the new >> raptor_world class. In Raptor 2.0 this initialisation and cleanup method >> will be removed. ]]] >> >> Initialization is clear: I just put it into the handled sequence of >> statements of the package (should I also add Elaborate and/or >> Elaborate_Body pragma?) >> >> But how to do cleanup? That is, where to call raptor_finish()? >> >> One way is to create a Limited_Controlled object in the package. Is there >> a simpler way? > > It is simple enough. > > But much simpler is not to call raptor_finish() at all. > > If the library is not OS-conformant, to clean up its internal persistent > state (does it have any?) upon unloading its instance, for example, when > the client application unexpectedly crashes, such a library must be > removed from the computer ASAP and never installed again. I disagree: It is quite legitimate for a library to create a temporary file, which may be deleted in library cleanup. -- Victor Porton - http://portonvictor.org