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 » Suggest Xmlize support for Value
Re: Suggest Xmlize support for Value [message #16134 is a reply to message #16123] Wed, 28 May 2008 21:51 Go to previous messageGo to previous message
Mindtraveller is currently offline  Mindtraveller
Messages: 917
Registered: August 2007
Location: Russia, Moscow rgn.
Experienced Contributor

Because it handles with hierarchical config data very conveniently. You should not write your own binary containers. Moreover, data could be partially binary and partially textual. I heavily use this feature i.e. for saving library of objects with dynamic properties. This means I don`t know types of each property at compile time, as user may add properties of any common type. This looks like rather common task and Xmlize works great for this (I even stopped writing my own XmlProperties class when implemented Value support for Xmlize).

Binding to binary format looks like a serious problem. But do we really do it? What we do is writing the same data output we have for all the types but in "textual" format. We could have the same output on all the platforms. The same bytes. My method simply emulates reading binary bytes. The same bytes you would read by using "direct" method. This is as far as I understand, maybe it`s not that simple though.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Upp::Time::Get() missing const
Next Topic: Can we get a Join that uses WString?
Goto Forum:
  


Current Time: Thu May 09 15:44:19 CEST 2024

Total time taken to generate the page: 0.01310 seconds