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

Re: genx - abstract output

• To: xml-dev@l...
• Subject: Re: genx - abstract output
• From: Michael Fuller <msf@m...>
• Date: Fri, 23 Jan 2004 10:50:25 +1100
• In-reply-to: <20040122070336.GB8151@p...>
• Mail-followup-to: Michael Fuller <msf@m...>,xml-dev@l...
• References: <A03C8438-4C8C-11D8-905C-000A95A51C9E@t...> <20040122035409.GD18459@m...> <20040122052954.GA2995@p...> <984DC92C-4C9F-11D8-905C-000A95A51C9E@t...> <20040122070336.GB8151@p...>

On Thu, Jan 22, 2004 at 02:03:36AM -0500, Adam Turoff wrote:
> On Wed, Jan 21, 2004 at 09:55:34PM -0800, Tim Bray wrote:
> > So, *why* do you want to serialize it?  To write it to a file or down a 
> > pipe to some other process, I'd say.  
> 
> Or a remote process through a socket.  Or stuffing into a database/DBM file.  

+1.

Using file descriptors (under Unix) and Handles (under Windows)
hides the distinction between files, pipes, sockets, etc.
I suppose one can always use fdopen(3C), for example, to convert
the descriptors created by pipe(2) into FILE*s, but...

M.

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

• Prev by Date: Re: genx - genxEndTag
• Next by Date: Re: genx - consensus items
• Previous by thread: Re: My review of genx.h
• Next by thread: Re: genx - abstract output
• Index(es):
  • Date
  • Thread