Re: XML-SAX *XML_EXCEPTION event and reported parsed length question -- RPG400-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: XML-SAX *XML_EXCEPTION event and reported parsed length question
From: Nathan Andelin <nandelin@xxxxxxxxx>
Date: Thu, 13 Jul 2017 09:52:24 -0600
List-archive: <http://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

That makes sense. But it underscores that the developer must know the
content of the XML document in order to instruct the parser on how to parse
it.

I should clarify, that the developer must provide instructions to the
parser about which portions of the document to parse - that the parser must
be invoked repetitively in order to extract the specific content needed -
and that repeated invoking of the parser is probably not as efficient as a
single pass would be.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: XML-SAX *XML_EXCEPTION event and reported parsed length question , Vernon Hamberg

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.