[pacman-dev] [PATCH] Fix memleaks in front-end caused by dynamic memory allocation

2008-10-24 Thread Nagy Gabor
http://repo.or.cz/w/pacman-ng.git?a=shortlog;h=refs/heads/working I know you may not like this way (free functions public), but IMHO the result is not so ugly ;-) Off-topic: A small thing. During working on this patch I realized, that "\nerrors occurred, no packages were upgraded.\n" messag

Re: [pacman-dev] [PATCH] Fix memleaks in front-end caused by dynamic memory allocation

2008-10-24 Thread Dan McGee
On Fri, Oct 24, 2008 at 12:00 PM, Nagy Gabor <[EMAIL PROTECTED]> wrote: > http://repo.or.cz/w/pacman-ng.git?a=shortlog;h=refs/heads/working > > I know you may not like this way (free functions public), but IMHO the > result is not so ugly ;-) Can we just expose something more like "free_conflictli

Re: [pacman-dev] [PATCH] Fix memleaks in front-end caused by dynamic memory allocation

2008-10-24 Thread Nagy Gabor
On Fri, Oct 24, 2008 at 12:00 PM, Nagy Gabor <[EMAIL PROTECTED]> wrote: http://repo.or.cz/w/pacman-ng.git?a=shortlog;h=refs/heads/working I know you may not like this way (free functions public), but IMHO the result is not so ugly ;-) Can we just expose something more like "free_conflictlist"?

Re: [pacman-dev] [PATCH] Fix memleaks in front-end caused by dynamic memory allocation

2008-10-24 Thread Aaron Griffin
On Fri, Oct 24, 2008 at 4:03 PM, Dan McGee <[EMAIL PROTECTED]> wrote: > Can we just expose something more like "free_conflictlist"? Having > those casts and stuff is rather ugly on the public side of the library > usage. I was always a fan of the libraries that did something of the sort: struct l