Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!agate!dog.ee.lbl.gov!nosc!crash!pro-harvest.cts.com!bclark
From: bclark@pro-harvest.cts.com (Brian Clark)
Newsgroups: comp.sys.apple2
Subject: Re: More ORCA/C bugs
Message-ID: <7847@crash.cts.com>
Date: 7 Mar 91 12:36:12 GMT
Sender: root@crash.cts.com
Lines: 30

In-Reply-To: message from neufeld@aurora.physics.utoronto.ca

>From: neufeld@aurora.physics.utoronto.ca (Christopher Neufeld)
>
>   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.
>

I've had this happen to me also... The funniest thing is that I can get
the fprintf(stderr, "8^)"); to work fine if the text editor isn't memory
resident... (I'm using only the text shell and editor, not Prizm). A hack
to get the editor out of memory is this stupid program:
This purges everything purgable from memory as you can guess.

#include <orca.h>
#include <memory.h>
void main (void) { NewHandle ( TotalMem(), userid(), 0x0000, NIL ); }

I believe ORCA/M customers have an update to the shell/editor, but I have
not seen an update offer for ORCA/C customers. My guess is that ByteWorks
is waiting till they finish more revisions on ORCA/C itself rather than
just the shell and/or text enviorment editor. Prizm needs work also.
 ___________________________________________________________________
|                  |||                                              |
|   Brian Clark    |||  \    ProLine:  bclark@pro-harvest           |
|------------------|-|--=>  InterNet:  bclark@pro-harvest.cts.com   |
| "][gs Forever!!" |||  /       UUCP:  crash!pro-harvest!bclark     |
|__________________|||______________________________________________|