Re: array handles and non-local exits

[Neil Jerram]

address@hidden (Ludovic Courtès) writes:

> Not quite.  If get/release are left as is (i.e., they do not establish a
> dynwind context), I would write something along the lines of:
>
>      You must take care to always unreserve an array after reserving it,
>   also in the presence of non-local exits.  If a non-local exit can
>   happen between these two calls, you should install a dynwind context
>   that releases the array when it is left (see Dynamic Wind).
>
>      In addition, array reserving and unreserving must be properly
>   paired.  For instance, when reserving two or more arrays in a certain
>   order, you need to unreserve them in the opposite order.
>
> I would simply remove the following paragraph:
>
>      These calls and other pairs of calls that establish dynwind contexts
>   need to be properly nested.  If you begin a context prior to reserving
>   an array, you need to unreserve the array before ending the context.
>   Likewise, when reserving two or more arrays in a certain order, you
>   need to unreserve them in the opposite order.
>
> What do you think?

Another loose end...  I agree and have committed your suggested text
to branch_release-1-8 and master.

Regards,
        Neil