• From: Tim Bray <tbray@t...>
• To: David Megginson <ak117@f...>
• Date: Sat, 13 Dec 1997 18:22:52 -0800

At 09:01 PM 13/12/97 -0500, David Megginson wrote:
>I have worried about this myself.  My design goal with Ælfred has been
>to limit myself to two class files: one for the parser itself, and one
>for the interface for the callbacks -- hence the separate event for
>attributes.  This decision has forced some pretty severely hacked-up
>internal code accompanied by very careful documentation.

Hmm, isn't this what JAR and so on are for?  Seems like an awfully 
severe design constraint.  I certainly agree with "small" as a design
goal, but it seems like limiting class file count carries a pretty
high price. - Tim

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • Re: YAXPAPI (Yet Another XML Parser API)- an XDEV proposal
    • From: David Megginson <ak117@f...>

• Prev by Date: Re: YAXPAPI (Yet Another XML Parser API)- an XDEV proposal
• Next by Date: Re: YAXPAPI (Yet Another XML Parser API)- an XDEV proposal
• Previous by thread: Re: YAXPAPI (Yet Another XML Parser API)- an XDEV proposal
• Next by thread: Re: YAXPAPI (Yet Another XML Parser API)- an XDEV proposal
• Index(es):
  • Date
  • Thread