On 2011-08-07 18:15, Sean Kelly wrote:
I was mostly wondering if the serialized was all template code or if the
archived portion used some form of polymorphism. Sounds like its the latter.
The serializer uses template methods, the archive uses interfaces and
virtual methods.
Sent from my iPhone
On Aug 7, 2011, at 8:19 AM, Jacob Carlborg<d...@me.com> wrote:
On 2011-08-07 02:24, Sean Kelly wrote:
Is the archive formatter dynamically pluggable?
I'm not exactly sure what you mean but you can create new archive types and use
them with the existing serializer. When creating a new serializer it takes an
archive (as an interface) as a parameter.
Sent from my iPhone
On Aug 6, 2011, at 11:51 AM, Jacob Carlborg<d...@me.com> wrote:
On 2011-08-06 18:32, Sean Kelly wrote:
I'd love to be able to send classes between processes, but first we need a good
serialization/deserialization mechanism.
Have a look at Orange, I don't know if it's considered good but it works for
almost all types available in D, the only available archive is currently XML.
http://dsource.org/projects/orange/
--
/Jacob Carlborg
--
/Jacob Carlborg
--
/Jacob Carlborg
