Ken wrote:
- Really, this overuse of strcpy/strcat results from our usage of fixed
sized buffers. We should be switching to dynamically-allocated strings
whenever possible. Fixing that means dealing with idea of who actually
owns a particular memory object and is responsible for freeing it?
I've been fixing up APIs I'm involved with, but it's slow going. I'd
rather address these problems this way rather than do a whole audit
for every instance of strcpy().
Agreed. The nmh MIME parser relies on dynamically-allocated
strings, and nicely at that. That's much more important to me
than a bulletproof config parser and outgoing message handler.
Its memory management is pretty clear from the structs and
comments in h/mhparse.h.
David
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers