I've pushed a "fix" for the problem which manifested itself as a leak
in test 274.
I use the word "fix" loosely. This commit:
1. Does indeed fix the leak that we identified.
2. So far as I am aware, does not introduce any new problems which did
not already exist.
3. Makes the code IMO sli
On Thu, Jun 27, 2013 at 08:21:12AM +0200, John Darrington wrote:
> On Wed, Jun 26, 2013 at 10:59:58PM -0700, Ben Pfaff wrote:
> On Wed, Jun 26, 2013 at 08:05:44AM +0200, John Darrington wrote:
> > I suggest that we divide up the work. Ben can you look at tests
> > 169 171 and 174 --