On Sun, May 26, 2013 at 11:53 AM, Henk Langeveld <[email protected]> wrote: > >> > >> http://stackoverflow.com/questions/16742136/ways-to-parse-json-using-kornshell >> > >> > So my question would be: What options are there for *builtin* json >> support? As json is quickly gaining traction as >> > a data-exchange format over xml, it would be nice to translate >> compounds to json and back. > > > A. P. Garcia wrote: >> >> In a nutshell, you write an extension and load it into ksh with the >> dynamic linker. >> >> I slightly prefer xml over json, but admittedly there isn't a big >> difference. I found this intriguing food for thought: >> >> http://forums.xkcd.com/viewtopic.php?f=40&t=77634 > > > Thanks for that. > > Quick summary: The author of that piece praises Powershell for > pipes that pass on objects in stead of unformatted text, and > makes a case for a next-gen unix cli built on similar principles. > > If you think about it, the concept of the unix command as a 'filter' is akin > to functional > programming; they consume input (stdin+parameters), produce output, and > leave no side-effects.
haven't you read Roland Mainz's comments about passing compound variables via pipe or network sockets? ksh93 already has a powerful (much more feature rich in what PowerShell can do) mechanism with that, and only at the beginning or the end a conversion from or to XML/JSON might be useful. In between the compound variable mechanism is much faster and flexible. Irek _______________________________________________ ast-users mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-users
