On 10/24/10 1:05 CDT, Robert Jacques wrote:
Unfortunately, This[string] currently causes an ICE. There's some
documentation in Variant that self referential types are not yet
supported. Also, I've found that using opDispatch to mimic fields, i.e.
foo.bar instead of foo["bar"], to be quite convenient. Would this be a
good feature candidate for inclusion in VariantN? Also, I'm not up to
date regarding VariantN bugs. Are they things you can work around, or
are they blocked by compiler issues?
Definitely that issue needs to be looked at. I think it's a compiler
bug, but then I didn't try real hard to avoid it.
Building on Algebraic would save a lot of work, and any further
improvements in Algebraic will help json too.
* The function parseJSON takes a range but not by reference, which
means there is no way for the caller to know the new range position
after having parsed one json object.
My parser takes an input range by ref.
* toJSON returns a string, which is inefficient for large objects. It
should take an output range.
My writer takes an output range by ref. I have a compact writer, a
pretty print writer and a toJsonString convenience function.
Then you may want to submit your code for review.
Andrei
_______________________________________________
phobos mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/phobos
