I'm studying how MGI's Read/Write Anything VIs might evolve to handle objects in human readable fashion. The result would be closely related or intertwined with the Character Lineator that Aristos Queue is working on. Therefore, I implemented an INI file compatible serializer/deserializer using his template to see how that would work. This Serializer/Deserializer passes all the same tests as the JSON version, except where a LabVIEW timestamp limitation causes problems, as discussed elsewhere. Two further notes:
1. Even though the Variant test passes, Variant handling is buggy. The JSON version has problems too, so I hypothesize that the problem is in AQ's code at the moment.
2. The floating point test is also weak. The formatter is using fractional instead of exponential notation, so other data values would fail. Does JSON require fractional notation?
> Does JSON require fractional notation?
Yes and no. JSON allows for the exponential notation, but all methods for producing that in LV appear to be precision lossy.
Variants appear to be fine for INI and JSON. Bugs were in the test code (not all data serialized/deserialized).
And people think I'm nuts when I ask if they have a test harness for their test harness.
I think we need a test harness for the test harness writer.
All testing should be done by the gimp? [Pulp Fiction reference]
AristosQueue Nov 30, 2012 5:26 PM (in response to DavidAMoore)
And people think I'm nuts when I ask if they have a test harness for their test harness.
Nah, - people think your nuts at other times too!