30 messages in com.mysql.lists.plusplusRe: Eyeballs needed on new reference ...
FromSent OnAttachments
Warren Young14 Aug 2007 23:26 
Chris Frey15 Aug 2007 01:14 
Alex Burton15 Aug 2007 01:42 
Joseph Artsimovich15 Aug 2007 01:56 
Joel Fielder15 Aug 2007 02:29 
Robert Mecklenburg15 Aug 2007 07:47 
Graham Reitz15 Aug 2007 08:38 
Graham Reitz15 Aug 2007 08:47 
Graham Reitz15 Aug 2007 09:03 
Jonathan Wakely15 Aug 2007 15:06 
Warren Young16 Aug 2007 01:55 
Warren Young16 Aug 2007 02:23 
Warren Young16 Aug 2007 02:31 
Warren Young16 Aug 2007 02:57 
Warren Young16 Aug 2007 03:08 
Warren Young16 Aug 2007 03:11 
Jonathan Wakely17 Aug 2007 17:54 
Jonathan Wakely17 Aug 2007 18:00 
Warren Young20 Aug 2007 12:09 
Warren Young29 Nov 2007 00:04 
Joseph Artsimovich29 Nov 2007 04:20 
Warren Young29 Nov 2007 05:48 
Jonathan Wakely29 Nov 2007 17:40 
Jonathan Wakely29 Nov 2007 17:58 
Jonathan Wakely29 Nov 2007 18:15 
Warren Young30 Nov 2007 22:24 
Warren Young30 Nov 2007 22:35 
Warren Young30 Nov 2007 22:38 
Warren Young17 Dec 2007 05:53 
Jonathan Wakely17 Dec 2007 12:39 
Subject:Re: Eyeballs needed on new reference counted pointer template
From:Warren Young (mysq@etr-usa.com)
Date:08/20/2007 12:09:09 PM
List:com.mysql.lists.plusplus

Jonathan Wakely wrote:

there's a race on the memory allocation in ResUse::field_types(int).

I'm pretty sure the whole create-on-demand strategy used with FieldNames and FieldTypes is a crock, but I haven't put in the time to prove it yet. Aside from the thread safety implications, it means you have to test the pointer all the time to be sure it's allocated, and if not, repeat the allocation code inline. Bleh.

At *minimum* we need to hide the pointer behind an accessor that wraps all this. If we can just allocate it on object creation without horrible consequences, so much the better.