Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!udel!haven!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.sys.apple2
Subject: Re: More ORCA/C bugs
Message-ID: <15370@smoke.brl.mil>
Date: 3 Mar 91 04:51:34 GMT
References: <17990@csli.Stanford.EDU> <1991Mar2.192847.12622@helios.physics.utoronto.ca>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 16

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?

So far as I know, it should work just fine -- providing that your code
is strictly conforming (i.e. you need to #include <stdio.h>).

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

The arrow will be visible if the entire path to the source file,
including all directories and the file itself, use only UPPER-case
characters.  This deficiency in PRIZM is supposed to be fixed in a
forthcoming release.