be adaptive about deleting the realloc filter
authorZefram <zefram@fysh.org>
Wed, 1 Feb 2012 21:40:24 +0000 (21:40 +0000)
committerZefram <zefram@fysh.org>
Wed, 1 Feb 2012 21:40:24 +0000 (21:40 +0000)
commit4e9e26b62d00dcf657478bae02c37745f15be9f6
treefe8a37b0261d8132e66a3954e75183be1c14f511
parent2627a85c12f756943124bdcb933b4d65d06e996f
be adaptive about deleting the realloc filter

Filters can only be deleted in the correct order (reverse of the order in
which they were added).  Insisting on deleting the filter would break if
another filter were added after ours and is still around.  Not deleting
the filter at all would break if another filter were added earlier and
attempts to delete itself later.  We can play nicely to the maximum
possible extent by deleting our filter iff it is currently deletable
(i.e., it is on the top of the filter stack).  Can still run into trouble
in more complex situations, but can't avoid that.
Changes
Declare.xs
t/filter0.t [new file with mode: 0644]
t/filter1.t [new file with mode: 0644]