Hi Rony, good idea. I want to feature freeze as soon as possible, so there is a good chance that nothing of rxapi, translation or JSON will make 5.0.0, the reason being that we need to focus on our delivery pipeline first. As soon as we can fully and repeatably implement this build, test, package automation thing, there is room for functional discussions. Which does not mean that we cannot prepare already: how should we implement this, while at the same time avoiding the Java problems introduced when XML Parsing and xslt were introduced: bad integration with external packages, even JVM versions among each other, the introduction of the ‘blessed extensions’ directory for this reason (now finally discontinued in JVM 1.9) - that is what we should not do. Ever needed to make build procedures for projects that freely integrated Sun and IBM JVM functionality, and Java and SAXON XSLT processors - all time pressured of course - it is not big fun.
When we branch for 5.00 we can start work on this right away; my hopes are that some brilliant mind can devise a scheme to parse XML, JSON, YAML etc and make it look like PARSE. At several points I have attempted to make parse do recursive descent and it always did the job but I was never quite satisfied with the results, tho I think it can be done. By the way, we do not only need parsing, we also need production. Last year, I needed to produce some JSON by hand for charts in a monitoring tool and it was a royal pain, making me remember XML in a different and much better light. best regards, René. > On 8 jul. 2016, at 11:45, Rony G. Flatscher <[email protected]> wrote: > > In the past years the JSON encoding has become dominant, not only in the > context of web > applications, but as a general encoding scheme for exchanging (structural) > data via text encodings. > Its definition is quite simple compared to XML DTD/XSD and "laymen" are able > to grasp the data > encoded in JSON and their structure immediately. > > A few years ago Brandon Cherry had an ooRexx class to parse and generate JSON > encoded text files. It > can be located e.g. at <http://www.idenburg.net/ooRexx/>. (If I am not > mistaken Brandon Cherry used > to have a sandbox directory in the oorexx project with that ooRexx package, > but it seems to have gone.) > > Given the ubiquitousness of JSON text encodings in modern programs it would > be quite important/a > real boon, if ooRexx 5.0 had this class available. (Very much like the > methods "encodeBase64" and > "decodeBase64" that got added to the .String class to make it easy for ooRexx > programmers to handle > that prominent and popular encoding scheme.) > > ---rony > > > ------------------------------------------------------------------------------ > Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San > Francisco, CA to explore cutting-edge tech and listen to tech luminaries > present their vision of the future. This family event has something for > everyone, including kids. Get more information and register today. > http://sdm.link/attshape > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel 1,9 ------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
