Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » U++ Core » Optional serialization techniques
Re: Optional serialization techniques [message #31378 is a reply to message #31371] Sat, 26 February 2011 07:49 Go to previous messageGo to previous message
tojocky is currently offline  tojocky
Messages: 607
Registered: April 2008
Location: UK
Contributor

mirek wrote on Fri, 25 February 2011 20:42



I guess the main problem is that it is so simple to serialize things that it is too easy to accidentally break the format...

And, sometimes, the problem also is that it is impossible or too diffuclt to keep backward compatibility. Simple example would be forgetting to put 'version' somewhere...

Mirek


Mirek, What about to migrate to a XML serialization? The things will be easy!
Your realization is very nice, but debugging and keeping backward compatibility is a little hard.

[Updated on: Sat, 26 February 2011 08:10]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: do upp have an equivalent of "eval()" in Javascript
Next Topic: Core/Path.cpp: the limitation of GetCurrentDirectory for POSIX
Goto Forum:
  


Current Time: Tue Aug 26 06:16:34 CEST 2025

Total time taken to generate the page: 0.06129 seconds