Lists Home |
Date Index |
- From: John Cowan <firstname.lastname@example.org>
- To: XML Dev <email@example.com>
- Date: Tue, 09 Mar 1999 12:10:31 -0500
Glenn Vanderburg wrote:
> First: let's not use exceptions to report non-error conditions. There
> are theoretical and practical reasons to restrict the use of Java
> exceptions to reporting errors.
We should take this off-line. I'll simply say: exceptions are
suitable for reporting exceptional conditions. Having an object
request its own replacement is certainly exceptional.
> Second: if an application needs to implement certain features by
> pushing filters from the bottom,
The idea here is that an application may request a feature which
a parser does not itself support, but can be adapted to support
by pushing a filter between itself and the application. That
of course requires that the application now talk to the filter
instead. (In principle, the parser could act as an adapter for
the filter, but that would complicated the bejesus out of it.)
In Smalltalk, the parser could swap object ids with the
filter using the become: method, but AFAIK no other OO language
John Cowan http://www.ccil.org/~cowan firstname.lastname@example.org
You tollerday donsk? N. You tolkatiff scowegian? Nn.
You spigotty anglease? Nnn. You phonio saxo? Nnnn.
Clear all so! 'Tis a Jute.... (Finnegans Wake 16.5)
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)