Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!xanth!ames!dftsrv!chrpserv!seiler From: seiler@chrpserv.gsfc.nasa.gov (Ed Seiler) Newsgroups: comp.sys.mac.programmer Subject: Re: stdin and stdout in MPW C 3.0 Keywords: stdin, stdout, MPW 3.0 Message-ID: <502@dftsrv.gsfc.nasa.gov> Date: 11 Oct 89 23:29:53 GMT References: <501@dftsrv.gsfc.nasa.gov> <16055@dartvax.Dartmouth.EDU> Sender: news@dftsrv.gsfc.nasa.gov Reply-To: seiler@chrpserv.gsfc.nasa.gov (Ed Seiler) Organization: Goddard Space Flight Center Lines: 29 In article <16055@dartvax.Dartmouth.EDU> earleh@eleazar.dartmouth.edu (Earle R. Horton) writes: > >It is possible to redirect stdin and stdout so that output goes to a >window you specify and input comes from the keyboard. In fact, there >is a package of routines you can get from Apple called WritelnWindow >that sets the whole thing up for you. WritelnWindow is intended for >debugging only, and you are not allowed to include it in applications >that you ship. It is, however, not hard to see how WritelnWindow >works, and one could write one's own console emulator, with hooks to >be driven off of stdio, and not violate any Apple stipulations. ... >The arrangement of the MPW runtime libraries is not optimum for the >creation of Macintosh applications. I believe that that is what you >wanted to hear. Unfortunately, there is not enough documentation >supplied so that you know enough to rearrange things, without spending >a lot of wasted time hacking around in object dumps. Actually, it's not so much a desire to be rid of stdio that I'm concerned about, but rather why the documentation doesn't mention, right in the beginning of the section about the stdio routines where it belongs, something such as "The C stdio routines are provided for the development of MPW tools. Developers who wish to perform I/O to a console should use toolbox routines (or get a hold of WriteInWindow)". It seems that the documentation assumes the MPW C developer already knows such minutiae. Is WriteInWindow a product available from APDA? Can the redirection of stdin and stdout to a window be described briefly? Ed Seiler