On Wed, 2006-07-26 at 21:01 -0500, Kevin P. Fleming wrote: > Should we just move this into a common place, now that it's being repeated in > quite a few places?
I certainly think that would be a good idea. I just couldn't decide where to put it. Then, I just decided to at least have the bugs fixed until I had an idea for what to do with it. > Alternatively, since we have ast_malloc/ast_calloc, should we have ast_free > (not in 1.2, of course)? I suppose. However, I'm not sure how beneficial it would be other than for matching the naming convention of the allocation wrappers. There is obviously no error checking we can do on a call to free(), so we can't inject an Asterisk log message or anything. -- Russell Bryant Software Developer Digium, Inc. _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
