Re:ASCII Delimited Text – Not CSV or TAB delimited text
by Pxtl on Wednesday March 26, 2014 @01:55PM
(#7475080)
Absolutely. Too bad they went for a flat format instead of a sexpr-like format. You wouldn't even need 4 characters - just start,end, and separator.
Re:ASCII Delimited Text – Not CSV or TAB delimited text
by jimmaswell on Wednesday March 26, 2014 @04:21PM
(#7476310)
if the object is given a UUID, the recursive data structure can just point to the UUID when it's serialized to this? what's the problem?
Re:ASCII Delimited Text – Not CSV or TAB delimited text
by stcredzero on Thursday March 27, 2014 @06:19AM
(#7479470)
Then you'd have 2 problems.
Re:ASCII Delimited Text – Not CSV or TAB delimited text
by jimmaswell on Thursday March 27, 2014 @10:50AM
(#7480702)
If I'm serializing nodes to ascii, and the rows are objects of type Node, and their contents were their UUID then VAL then NEXT, NEXT being a UUID, I don't see how you have 2 problems now.
I think the more fundamental problem with using the ASCII control characters is that there's no way (or rather, no obvious and standard way AFAICS) to use them to define (most) recursive data structures. That's not a problem when you stick to simple CSV-like arrays-of-arrays, but it's enough of a restriction to make one wonder if bringing ASCII back is worth the battles.