Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!apple!usc!jarthur!nntp-server.caltech.edu!tybalt.caltech.edu!toddpw
From: toddpw@tybalt.caltech.edu (Todd P. Whitesel)
Newsgroups: comp.sys.apple2
Subject: Re: Orca/C, bug?
Keywords: Orca/C
Message-ID: <1990Oct18.023155.17388@nntp-server.caltech.edu>
Date: 18 Oct 90 02:31:55 GMT
References: <11906@bsu-cs.bsu.edu> <1990Oct18.015919.15150@ux1.cso.uiuc.edu>
Sender: news@nntp-server.caltech.edu
Distribution: usa
Organization: California Institute of Technology, Pasadena
Lines: 15
Nntp-Posting-Host: tybalt.caltech.edu

jb10320@uxa.cso.uiuc.edu (Desdinova) writes:

>   Orca DOES require a typecast.  But it doesn't complain. One of the
>biggest problems with ORCA is it's lack of error messages, or inappropriate
>error messages.  It's makes programming difficult sometimes.

Funny... I've found the error messages to be a fairly good safety net.
The only three things I'd run into before this were the structure auto-
initialization bug, a problem with using fread and fwrite (i.e. they trash
memory in subtle ways), and an inability to declare a pointer to void as a
normal variable or element of a structure (ANSI K&R is a little vague on
whether you can actually do that -- anybody know?).

Todd Whitesel
toddpw @ tybalt.caltech.edu