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 » ValueArray behaviour / inconsistantcy / BUG?
Re: ValueArray behaviour / inconsistantcy / BUG? [message #29468 is a reply to message #29465] Fri, 22 October 2010 09:53 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 13984
Registered: November 2005
Ultimate Member
kohait00 wrote on Fri, 22 October 2010 01:30

tested, bug is gone, thanks Smile

BTW: what about the
void ValueArrayXmlize(XmlIO xml, Value& v)
{
	if(xml.IsStoring())
	{
		const ValueArray& va = v;
		XmlizeStore(xml, va.Get());
	}
	if(xml.IsLoading())
	{
		Vector<Value> vv;
		::Xmlize(xml, vv);
		v = ValueArray(vv);
	}
}
INITBLOCK { RegisterValueXmlize(GetValueTypeNo<ValueArray>(), &ValueArrayXmlize, "ValueArray"); }

does it make sense to provide it in Core?


No.

But what would make sense is:

Xmlize specialization for ValueArray and ValueMap.

Backward compatible change of Xmlize of Value that would handle 'basic known' types (that would include ValueArray) more gently, without binary serialization.

[Updated on: Fri, 22 October 2010 09:54]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: First use of SetVppLogName will call sOpenVppLog twice
Next Topic: Middle-ground between CONSOLE_APP_MAIN and GUI_APP_MAIN
Goto Forum:
  


Current Time: Mon Jun 10 14:25:42 CEST 2024

Total time taken to generate the page: 0.02209 seconds