[Aldor-l] Code audit

[Pippijn van Steenhoven]

On Mon, Jun 30, 2008 at 10:47:51AM -0700, David Casperson wrote:
> buffer points at, just the buffer itself.  This matches
> bufCapture, which does not copy the ``String s'', just makes a
> buffer that points at it.
>
> Does this seem right?

It seems right, but in some cases (dgCycleError, dgOrderError), the
buffer is created with bufNew, not bufCapture. Your explanation of
"memory leak is okay on error paths" is not really what I'm looking for.
As I explained on my website, the Aldor GC performs best if memory is
manually returned to the allocator. Am I missing anything here? Is
bufLiberate really the right thing even in these functions?

-- 
Pippijn van Steenhoven
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://aldor.org/pipermail/aldor-l_aldor.org/attachments/20080703/7a5fbaea/attachment.bin