Re: POPT's API has designed in memory leaks. What to do?

2016-02-15 Thread Seonkon Choi
On Thu, Jun 17, 2010 at 10:09:37AM -0400, Jeff Johnson wrote: > > On Jun 17, 2010, at 4:27 AM, Markdv wrote: > > > > > I just don't see why you wouldn't want to "fix" this. Seems like all you'd > > have to do is add > > > >con->os->nextArg = _free(con->os->nextArg); > > > > to

Re: POPT's API has designed in memory leaks. What to do?

2010-06-07 Thread Jeff Johnson
On Jun 7, 2010, at 10:37 AM, Mark Hatle wrote: The way I've usually addressed this is to either add an option to the library that changes the default behavior from strdup to passing the address with the expectation of const. I'd rather _NOT_ go the Have it your own way! route in a