[gephex-devel] c++ linktypes

Martin Bayer martin at gephex.org
Tue Nov 23 16:40:46 CET 2004


[Georg Seidel]:
> ~   * maybe make the ascii serialisation optional by moving them
> ~     into an "AsciiSerializableLink" subclass (images and audio
> ~     data maybe wont allow serialization to ascii)

How do you what to use these optional functions from the subclass? Do 
you want to introduce a kind of typeid field in the base class or do you 
want to use RTTI?

 > virtual Link* create(alloc_fun_t gphx_alloc, free_fun_t gphx_free)=0;

Do you think it is possible to implement a placement in shared memory 
with these "functions"? I think would need (de)allocator objects and not 
only functions for this. Perhaps the binary serialization way is a 
slower but cleaner way for shared memory IPC.

Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://lists.gephex.org/pipermail/gephex-devel/attachments/20041123/2eb41891/signature.bin


More information about the gephex-devel mailing list