[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: genx - abstract output

• To: John Cowan <cowan@m...>
• Subject: Re: genx - abstract output
• From: Adam Turoff <ziggy@p...>
• Date: Thu, 22 Jan 2004 00:29:54 -0500
• Cc: Tim Bray <tbray@t...>, xml-dev@l...
• In-reply-to: <20040122035409.GD18459@m...>
• References: <A03C8438-4C8C-11D8-905C-000A95A51C9E@t...> <20040122035409.GD18459@m...>
• User-agent: Mutt/1.4.1i

On Wed, Jan 21, 2004 at 10:54:09PM -0500, John Cowan wrote:
> Tim Bray scripsit:
> > 2. If you're going to build an XML instance in memory, wouldn't it be 
> > more natural to pull together a DOM or your own private data structure 
> > and then serialize it in one fell swoop?

So I build a data structure and I'm ready to serialize it to XML.  But
there are a lot of nasty corner cases I don't want to mess up, so I want
a library to handle all of the details I'm likely to get wrong.  I'm
looking for something that guarantees valid XML output, or fails as soon
as possible.

Hm.  Sounds like genx to me.  ;-)  

> > 3. This lowers the barrier-to-entry to implementers, who are going to 
> > see genxStartDocument(genxWriter w, FILE * file) and say "oh yeah I 
> > know what to do" as opposed to having to figure out another flavor of 
> > I/O abstraction and write a stub of some kind.
> 
> A simple implementation strategy would be to keep the FILE * argument,
> but also provide a call to set/get an output handler, to be invoked only
> if the FILE * argument is NULL.  That makes easy things easy and hard
> things possible.

+1

A convenient escape hatch for (a) building an instance in memory, 
(b) transcoding, or (c) anything else, really.

Z.

• Follow-Ups:
  • Re: genx - abstract output
    • From: Tim Bray <tbray@t...>

• References:
  • genx - abstract output
    • From: Tim Bray <tbray@t...>
  • Re: genx - abstract output
    • From: John Cowan <cowan@m...>

• Prev by Date: Re: genx - string termination and bounding
• Next by Date: Re: genx - abstract output
• Previous by thread: Re: genx - abstract output
• Next by thread: Re: genx - abstract output
• Index(es):
  • Date
  • Thread