pthreads in guid.c break compile
Derek Atkins
warlord at MIT.EDU
Tue Jul 1 12:29:06 CDT 2003
Well, personally I think smattering a bunch of (relatively small)
buffers around the stack isn't a big deal.. I only suggested TLS
because you didn't like the solution of spattering a bunch of
(relatively small) buffers around. If the choice is static buffer
or TLS I'll take TLS... But I still maintain that I'd prefer the
smattering of buffers.
-derek
David Hampton <hampton at employees.org> writes:
> On Mon, 2003-06-30 at 17:40, Matthew Vanecek wrote:
> > To Derek's point, is pthreads the desired direction?
>
> I don't know. I was just trying to fix a memory leak. Derek's the one
> who insisted that I use thread local storage, which to me means
> pthreads. It was either that or splatter single use character arrays
> across the code base, which seems like entirely the wrong approach to
> me. As far as whether we should be using pthreads, I'll go with
> whatever group consensus is.
>
> David
>
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at lists.gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
warlord at MIT.EDU PGP key available
More information about the gnucash-devel
mailing list