Newsgroups: comp.sys.apple2
Path: utzoo!utgpu!news-server.csri.toronto.edu!helios.physics.utoronto.ca!aurora.physics.utoronto.ca!neufeld
From: neufeld@aurora.physics.utoronto.ca (Christopher Neufeld)
Subject: More ORCA/C bugs
Message-ID: <1991Mar2.192847.12622@helios.physics.utoronto.ca>
Sender: news@helios.physics.utoronto.ca (News Administrator)
Nntp-Posting-Host: aurora.physics.utoronto.ca
Organization: University of Toronto Physics/Astronomy/CITA
References: <17990@csli.Stanford.EDU>
Date: Sat, 2 Mar 1991 19:28:47 GMT

   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.
   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.
   When I had a doubly defined #define argument, it issued the
appropriate error message and line and column numbers in the source
file, but it echoed the line after the error, which was another #define.
It took me a while to figure out that the line echoed in the error
message was not the one which caused the offense.
   Is there any word on whether the upgrade will fix the problem in the
debugger which keeps the arrow from being visible, or the window from
scrolling to follow the arrow until after it makes its first subroutine
call, and sometimes not even then?


-- 
 Christopher Neufeld....Just a graduate student  | Note: new host.
 neufeld@aurora.physics.utoronto.ca    Ad astra! | helios will still
 cneufeld@{pnet91,pro-cco}.cts.com               | forward my mail to
 "Don't edit reality for the sake of simplicity" | me on aurora.