In message 0CE9572A.19991123110923.FOO-4A5F.frank@g-n-u.de Frank Heckenbach writes:

David James wrote: [snip]

...

However what I really want to do is to put this record into shared memory, so I moved to daj4u and dajunit4, attached. This fails. [snip] My question is really what is the recommended way to do this: is it to set the string's capacity, or should I be calling some other function to initialise the record proerly after I shmat the shared memory? I assume that new(record_pointer) is initialising string capacities within the record, somehow.

Oh, I see. That's a completely new thing, something which hasn't been tried with GPC yet. So, let's see, what would be a good solution here... [snip

• You could use some lower-level hooks into GPC's memory manager. These hooks already exist in the gpc unit (originally introduced to implement some BP compatible stuff in the system unit). They allow you to redirect any raw memory de-/allocations to user-defined routines, while GPC will still do all the initializations of strings, schemata, files, objects, etc.

Thank you, that seems to do everything I need at present. I can see I need to read gpc.pas more carefully to see what other nice features are in there.