Re: Could UNIX I/O be Made Type-Safe?
- From: David Schwartz <davids@xxxxxxxxxxxxx>
- Date: Mon, 5 Jan 2009 10:48:02 -0800 (PST)
On Jan 5, 10:20 am, Michael Mol <mike...@xxxxxxxxx> wrote:
Under Windows, data in the clipboard is advertised as being available
in any of a number of formats that the content provider supports, and
when another application goes to read from the clipboard, it may
select from any of the offered formats. The first few bytes of a
program's STDOUT could indicate the available formats. All that
remains is for the reading application to tell the provider which
format it wants.
It doesn't matter what the reading application wants. The purpose of
pipes is to give the redirect the output of one process to the input
of another, regardless of what either process wants. This is a logical
operation wherein the sending application chooses the format. It is
not in any way analogous to other operations where the recipient
chooses the format.
DS
.
- References:
- Could UNIX I/O be Made Type-Safe?
- From: Mattias Wikstrom
- Re: Could UNIX I/O be Made Type-Safe?
- From: David Schwartz
- Re: Could UNIX I/O be Made Type-Safe?
- From: Michael Mol
- Could UNIX I/O be Made Type-Safe?
- Prev by Date: Re: Could UNIX I/O be Made Type-Safe?
- Next by Date: Re: Could UNIX I/O be Made Type-Safe?
- Previous by thread: Re: Could UNIX I/O be Made Type-Safe?
- Next by thread: Re: Could UNIX I/O be Made Type-Safe?
- Index(es):
Relevant Pages
|
