Re: c++ linktypes

[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

_______________________________________________
gephex-devel mailing list
[email protected]
http://lists.gephex.org/mailman/listinfo/gephex-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBo1oGCm3i57PRsbsRAq4VAKCK4s9WJ22nOx0xRjcF6zzHtTnNRgCgty2S
QqB5lF46jL+0BSoxLQ7uhDY=
=CLq3
-----END PGP SIGNATURE-----