When I first started teaching/using YAJL (many years ago now) I
discussed both the event-based and tree-based approaches. I created
"simplified" wrappers for each in YAJLR4 -- but, honestly, I never got
around to testing the event-based ones... so the code there is
Why? Because the tree-style ones were so much easier to learn, use and
teach. I quickly found this was the only option people were really
interested in. The event-based (which is more like SAX) never sparked
As Jon said, I did use the event-based approach for the YAJLINTO program
(the DATA-INTO parser). I didn't use my "simplified wrappers", though -
I called the regular YAJL C routines directly. So that part definitely
works, and you can use the code in YAJLINTO as an example.
But, I'm wondering why you wouldn't use the tree-based (or
DATA-INTO/DATA-GEN) options? These are widely used and pretty much
everyone has agreed that it's easier... so, why not?
On 1/19/2022 4:14 PM, Alan Campin wrote:
Does anyone know of an example of using Scott Klement's YAJL in an eventin
driven mode (Like XML-SAX). There seems to be a lot of examples of using
Tree-Mode and using Data-Into.--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
Help support midrange.com by shopping at amazon.com with our affiliate
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.