Posted by
Plamen Neykov on
Jan 12, 2010; 6:10pm
URL: http://quantlib.414.s1.nabble.com/Serialisation-change-tp11630.html
Hi all,
I'd like to commit a small change to the serialisation code in
QuantLibAddin. It will remove the dependency of the serialised objects
to the order in which the ValueObjects are registered in the code so
that additions of new classes or removal of old ones will not break
the compatibility of existing xml archives. How this works is very
simple - a class id gets generated only when this class appears in the
archive for the very first time. This ensures that id's are local to
the archive and are only dependant on the classes serialised in this
archive.
The down side is that this will break all existing exports - however
those exports are anyway not very stable because chances are that they
get broken with any new class being added in QLA.
Please let me know what you guys think...
cheers,
Plamen
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
QuantLib-dev mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-dev