Open GoogleCodeExporter opened 9 years ago
I don't disagree, and it is something I've been playing with in my head for a
while. There are some aspects of the current decorator tree that are highly
related to protobuf, but perhaps a reasonable middle ground would be to
construct subtly different trees for different scenarios (for example, the way
lists are handled between xml and .proto would warrant a different decorator
implementation there).
This would (in theory) allow me to use most of the "meta" and "emit" layers,
and simply have a different reader/writer on the top, and perhaps a few minor
tweaks in the tree.
It is on my roadmap, but I plan on clearing down my backlog before tackling
this, as it is not without effort.
Original comment by marc.gravell
on 13 Jul 2011 at 10:59
I will be waiting for this development. It bears a great promise.
Thanks.
Original comment by mark.kha...@gmail.com
on 13 Jul 2011 at 11:07
Have a look at http://www.sharpserializer.com/en/index.html
It seems relevant.
Original comment by mark.kha...@gmail.com
on 20 Sep 2011 at 6:20
Original issue reported on code.google.com by
mark.kha...@gmail.com
on 13 Jul 2011 at 8:10