There is an alternative too. Instead of letting the user of s7 handle a pool of s7 instances, s7 could handle this pool itself so that s7_release (or s7_free) put the instance into this pool, and then s7_init would use this pool if possible. Wouldn't always be an acceptable solution, but maybe it's good enough.
On Thu, Sep 10, 2020 at 11:56 AM <[email protected]> wrote: > > I have started merging Woody's code -- s7_free in the current > tarball. This will not be done overnight. Thanks for the > pointer to mail-archive -- I'll check it out later today. > > _______________________________________________ > Cmdist mailing list > [email protected] > https://cm-mail.stanford.edu/mailman/listinfo/cmdist _______________________________________________ Cmdist mailing list [email protected] https://cm-mail.stanford.edu/mailman/listinfo/cmdist
