Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!news.cs.indiana.edu!ux1.cso.uiuc.edu!ernie!bazyar
From: bazyar@ernie (Jawaid Bazyar)
Newsgroups: comp.sys.apple2
Subject: Re: Orca C problems
Keywords: Orca,C
Message-ID: <1991Feb11.223046.727@ux1.cso.uiuc.edu>
Date: 11 Feb 91 22:30:46 GMT
References: <8323@ucdavis.ucdavis.edu> <1991Feb10.232157.3448@ddsw1.MCS.COM> <15159@smoke.brl.mil>
Sender: news@ux1.cso.uiuc.edu (News)
Reply-To: bazyar@cs.uiuc.edu (Jawaid Bazyar)
Organization: Mutation Testing Facility, University of Illinois
Lines: 17

In article <15159@smoke.brl.mil> gwyn@smoke.brl.mil (Doug Gwyn) writes:
>That's correct, but there is more that one should know, namely that
>some run-time functions REQUIRE support from a shell such as APW/Orca's.
>If you're developing stand-alone applications you need to avoid stdio etc.

  That's not necessarily true.  I have a program that uses TextTools (don't
tell me- I should use the GS/OS drivers) to change what happens to C's
stdout.  I install a routine of mine as the stdout driver, and whether
under the shell or as an S16 it works correctly.  I'm certain, however,
that the only thing in the Orca libraries that doesn't work under S16 is
the Shell interface calls.  Everything else gets linked in from ORCALIB.

--
Jawaid Bazyar               | "I'm sure K&R have never heard of Mike." 
Senior/Computer Engineering |
bazyar@cs.uiuc.edu          | "That's okay. I'm sure Mike's never heard of K&R".
   Apple II Forever!        |  (discussion about Orca/C)