Bug#531105: libtriangle-dev: Consider exposing trimalloc

2009-06-15 Thread Adam C Powell IV
On Sat, 2009-06-13 at 21:54 +0100, Francis Russell wrote: > > Sure, no problem. It sounds like you have something specific in mind -- > > and like you know the library better than I do. Would you be able to > > create a patch? > > I've only started using it recently, although I have noticed a fe

Bug#531105: libtriangle-dev: Consider exposing trimalloc

2009-06-13 Thread Francis Russell
> Sure, no problem. It sounds like you have something specific in mind -- > and like you know the library better than I do. Would you be able to > create a patch? I've only started using it recently, although I have noticed a few issues of varying importance. To be honest, most of these should p

Bug#531105: libtriangle-dev: Consider exposing trimalloc

2009-05-31 Thread Adam C Powell IV
On Sat, 2009-05-30 at 02:51 +0100, Francis Russell wrote: > Package: libtriangle-dev > Version: 1.6-2 > Severity: wishlist > > > This would be helpful because it would avoid having to keep track of which > memory blocks were allocated by the library or client as the client could also > use trimal

Bug#531105: libtriangle-dev: Consider exposing trimalloc

2009-05-29 Thread Francis Russell
Package: libtriangle-dev Version: 1.6-2 Severity: wishlist This would be helpful because it would avoid having to keep track of which memory blocks were allocated by the library or client as the client could also use trimalloc, making it possible to always use trifree to deallocate. -- System In