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: Re: More ORCA/C bugs
Message-ID: <1991Mar3.022734.16294@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> <1991Mar2.192847.12622@helios.physics.utoronto.ca> <1991Mar2.210621.21501@ux1.cso.uiuc.edu>
Date: Sun, 3 Mar 1991 02:27:34 GMT

In article <1991Mar2.210621.21501@ux1.cso.uiuc.edu> bazyar@cs.uiuc.edu (Jawaid Bazyar) writes:
>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.
>
   It worked for me a few times, then I lengthened the program and it
stopped working.

>>   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.
>
   I agree that using Prizm is an experience not to be enjoyed. I write
my programs from the shell on MicroEMACS. When it comes to debugging,
though, Prizm is less trouble than putting "printf()" commands
everywhere you'd like to check variables. The variables package also
doesn't handle arrays very well. I keep having to create dummy variables
and lines which assign array elements to the variable so that I can view
them with the variables package. Variables doesn't seem to handle
structure elements at all, though it will give the pointer to the
structure.

>   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.
>
   I'm glad to hear it. It's a very nice package, despite the annoying
problems with the desktop environment.


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