Hi Ken, > Although ... crud, I take your point that a small change is a lot > easier than a big change.
Yes, as soon as a free() is needed then there's tracking the paths that exit the function, where the pointer gets copied to, etc. GC anyone? :-) > My concern there is our release cycles have been long What needs to get done before 1.7 gets sent off to make its fortune? Is that soon enough that this could hold off? > and I'd hate to have code that barfs on emails released for a few > years. Perhaps a complainant could be told of the secret $NMHNOBARF to stop TRUNCCPY from aborting? Though it would still complain for the first N goes? -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy _______________________________________________ Nmh-workers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/nmh-workers
