Hi Eric, On Jan 8, 2004, at 3:07 PM, Eric Long wrote: Thanks for responding to my post. What happens if you manually change the type of that value from <real> to <integer>? I suspect the OSObject parser doesn't know anything about reals. I believe that's the problem. The call works if I make that change. Seems like the parser should handle it though. It seems inconsistent for the OS to support value types in one place and then not in another. The key is that floating point is discouraged in the kernel. Plus, the parser was intended to be used with OSObject serialization and not as a generic XML parser. Please feel free to file an enhancement request at <http://developer.apple.com/bugreporter> though. The app is using the standard OS functions to parse its plist file. We're not even enter the key/value pair. It's some underlying activity of Cocoa that is adding it to our file. Is there a specification for what values OSUnserializeXML() can and can't handle anywhere? No, other than the source. But I'd expect that anything that can be serialized via OSObject::serialize() and its subclasses would be unserializable. Thanks again, Eric You betcha, --gc _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.