Re: c++ linktypes

[Georg Seidel]
> but to keep it simple: serialize can just return 0 to indicate no
> serialization

A default implementation with return 0 is ok for me.

> |  > 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"?
> 
> Why do you quote those beautiful and regular funcions?

I didn't found a definition of alloc_fun_t and free_fun_t.

It could also be something like thing that:

class alloc_fun_t
{
   public:
     // get some memory ..
     void* operator(size_t size);

   private:
     some memorymanager stuff to remember;	
};

> And why not just use
> 
> ~  virtual Link* create()=0;
> 
> (we probably will never implement this shared memory stuff)

It would be problematic anyway with complex link types and 
syncronization. With binary serialization in a shared memory area 
syncronization is much easier.

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

iD8DBQFBo4lACm3i57PRsbsRAkY6AKCWyzMIKMYcNoyoeuuz40M2BJJ0PgCgxlpY
73FB7FWIptq4LFAJW/p0j2c=
=hDoV
-----END PGP SIGNATURE-----