I meant the opposite. Something that looks like a file but the stuff 
that is written to it goes to the printer or to the spooler, etc. I'm 
just pointing out that no special API should be necessary here for 
simple default printing from any OS that has a file system.

Cheers,

Alan

------

At 3:03 PM +0100 2/8/02, G.J.Tielemans at dinkel.utwente.nl wrote:
>1. under Windows you can define a pseudo-printer-file: form that moment on
>all your windows-programs think that it is one of the printers.
>
>2. Under windows you have Redmon
>http://www.cs.wisc.edu/~ghost/redmon/index.htm
>You use it to intercept (print)output from a program and redirect it to
>another program.
>
>
>
>-----Original Message-----
>From: Bert Freudenberg [mailto:bert at isg.cs.uni-magdeburg.de]
>Sent: Friday, February 08, 2002 2:32 PM
>To: squeak-dev at lists.squeakfoundation.org
>Subject: Re: squeak printing?
>
>
>On Fri, 8 Feb 2002, Alan Kay wrote:
>
>>  OK, why isn't the print spooler a pseudofile?
>
>IMHO, because it would be awkward to specify options for a pseudofile.
>Since on unix you can pipe the output of one program (your app) to the
>input of another program (the print spooler), it's as convenient as a
>pseudofile. You could in fact create a pseudofile ("named pipe") that
>looks like a file but connects to the spooler daemon.
>
>-- Bert


--