Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!news.cs.indiana.edu!ux1.cso.uiuc.edu!ernie!bazyar
From: bazyar@ernie (Jawaid Bazyar)
Newsgroups: comp.sys.apple2
Subject: Re: More ORCA/C bugs
Message-ID: <1991Mar2.210621.21501@ux1.cso.uiuc.edu>
Date: 2 Mar 91 21:06:21 GMT
References: <17990@csli.Stanford.EDU> <1991Mar2.192847.12622@helios.physics.utoronto.ca>
Sender: usenet@ux1.cso.uiuc.edu (News)
Reply-To: bazyar@cs.uiuc.edu (Jawaid Bazyar)
Organization: Mutation Testing Facility, University of Illinois
Lines: 27

In article <1991Mar2.192847.12622@helios.physics.utoronto.ca> neufeld@aurora.physics.utoronto.ca (Christopher Neufeld) writes:
>
>   I've been having some problems recently. Is there any reason that the
>command: fprintf(stderr,"Testing\n"); shouldn't work in a long program?
>I don't have to open the file, it's standard open when run from the
>shell. If I change it to printf("Testing\n"); everything works.
   fprintf(stderr,"Testing\n") has worked fine for me in programs.

>   Other weird things include programs which run fine, but if you use
>the "variables" command to monitor one of the variables, it immediately
>crashes Prizm into the monitor, until you rename the variable in the
>source code. No variable name conflicts were involved.

   Oh!  You're in Prizm.  Now I see the problem...

   Prizm isn't worth the iron it's encoded on.
Hopefully the new version will fix the almost infinite problems with Prizm,
and make it useful.
   Orca/C 1.2 is now in beta.  Mike says he's going to be working on it
thru next week.  1.2b1 has fixed 15 bugs supposedly.


--
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)