JSON: add write methods and implement unparse() in terms of those

1 files changed, 0 insertions, 11 deletions

diff --git a/TODO b/TODO
index ec110f34..d1bf0117 100644
--- a/TODO
+++ b/TODO
@@ -51,11 +51,6 @@ library, when context is available, to have a pipeline rather than a
 FILE* or std::ostream. This makes it possible for people to capture
 output more flexibly.
 
-JSON: rather than unparse() -> string, there should be write method
-that takes a pipeline and a depth. Then rewrite all the unparse
-methods to use it. This makes incremental write possible as well as
-writing arbitrarily large amounts of output.
-
 JSON::parse should work from an InputSource. BufferInputSource can
 already start with a std::string.
 
@@ -64,12 +59,6 @@ writes data to the pipeline. It's writer should create a Pl_Base64 ->
 Pl_Concatenate in front of the pipeline passed to write and call the
 function with that.
 
-Add methods needed to do incremental writes. Basically we need to
-expose functionality the array and dictionary unparse methods. Maybe
-we can have a DictionaryWriter and an ArrayWriter that deal with the
-first/depth logic and have writeElement or writeEntry(key, value)
-methods.
-
 For json output, do not unparse to string. Use the writers instead.
 Write incrementally. This changes ordering only, but we should be able
 manually update the test output for those cases. Objects should be