🚀 go-pugleaf

In article <cwatson-0102BE.20340207102003@aeinews.aei.ca>,
 Sean McBride <cwatson@cam.org> wrote:

> In article 
> <hinnant-CF8AA0.21254129092003@syrcnyrdrs-02-ge0.nyroc.rr.com>,
>  Howard Hinnant <hinnant@metrowerks.com> wrote:
> 
> > > It is not thread safe.  But it is simple enough it easily could be made 
> > > so.  Hmm... perhaps I'll write about the new Metrowerks::threads next. 
> > 
> > With the gauntlet thrown, and the overwhelming reader response just 
> > daring me to try and make this puppy thread safe, I just couldn't resist 
> > the challenge. :-)  (is that crickets I hear chirping?  oh never mind)
> 
> Any plans to replace the (non-thread safe) DebugNew with your new memory 
> debugger?  Or merge the two and include them with CW?

No such plans that I'm aware of.  My intent with simple_mem_debug was 
more along the lines of distributing a copyright-free basic memory 
debugger that was simple enough that everyone could customize it to 
their own needs, and yet still useful if you didn't enhance it at all.

And I must admit that simple_mem_debug is also a nice vehicle to show 
some practical use cases of a few Metrowerks extensions (hash_map, 
alloc_ptr, recursive_mutex, call_once). :-)

DebugNew still sports features that simple_mem_debug doesn't, for 
example:  DebugNewForgetLeaks(), DebugNewSetErrorHandler().  And then 
there is the backwards compatibility issue of changing the interface of 
DebugNew.

-Howard