Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!rex!uflorida!kluge!serss0!acmfiu
From: acmfiu@serss0.fiu.edu (ACMFIU)
Newsgroups: comp.sys.apple2
Subject: Re: More ORCA/C bugs
Message-ID: <2761@kluge.fiu.edu>
Date: 7 Mar 91 01:24:40 GMT
References: <17990@csli.Stanford.EDU> <1991Mar2.192847.12622@helios.physics.utoronto.ca>
Sender: news@kluge.fiu.edu
Organization: Florida International University, Miami
Lines: 37

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

Chris,
	i've also noticed these bugs. i have a 3000+ line program that i
	wrote and when you invoked it with a '-h' option for help on what
	further options were available, i used fprintf (stderr, <str>) to
	output the info. well, it didn't work. oddly enough, when i was
	going to report some bugs to mike last week i tried it again and it
	did work. i've been unable to recreate the bug as of yet. however,
	i am still hoping to do so. let mike know immediately about your bug
	as he's working on bug fixes now for the update to orca/c. call him
	if you can. if it's a small program, e-mail it to me and i will send
	it to him on america online.

	regarding prizm, you will see an updated version of prizm when orca/c
	v1.2 is released. i think that release of prizm should correct most of
	the bugs.

albert