Re: c++ linktypes

Georg Seidel <[email protected]>
Newsgroups gmane.comp.video.gephex.devel
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

|> ~   * 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?

I though about giving the type when loading the factory classes from
the plugin...
but to keep it simple: serialize can just return 0 to indicate no
serialization

|
|  > 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?
And why not just use

~  virtual Link* create()=0;

(we probably will never implement this shared memory stuff)

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

iD8DBQFBo4Hq/rP0cdKF/ToRAvkqAJ9LDaoRVnHiB56zF+E+ZZtMjO9jtACcCO6f
P+UrDMBQbyyD7ZNzEImz7T4=
=l+Mg
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.