Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!psuvax1!gatech!ncsuvx!ecemwl!jnh
From: jnh@ecemwl.ncsu.edu (Joseph N. Hall)
Newsgroups: comp.sys.mac.programmer
Subject: Re: C++ ... setting new standards for patience
Message-ID: <4221@ncsuvx.ncsu.edu>
Date: 18 Oct 89 11:42:56 GMT
References: <4208@ncsuvx.ncsu.edu> <4801@internal.Apple.COM>
Sender: news@ncsuvx.ncsu.edu
Reply-To: jnh@ecemwl.UUCP (Joseph N. Hall)
Organization: North Carolina State University
Lines: 36

In article <4801@internal.Apple.COM> lsr@Apple.COM (Larry Rosenstein) writes:
>Any error that is reported by the C compiler is a bug in CFront, no 
>question about it.  CFront is supposed to catch all the program syntax 
>errors, so you should never see errors reported by the C compiler. 

(If you're still there!)

Then this is the shortest amount of time it's ever taken me to find a
compiler bug ... about 2 hours.  The actual error message was:

# ?
### Error 213 Field name expected
----------------------------------------------------------------
    File "test.cp"; Find *!743:$!1; Open "{Target}"
#---------------------------------------------------------------

I had a class which had overloaded methods named X() and X(int arg),
respectively, used in the Smalltalk sense (obj.X() returns the value
of member x and obj.X(arg) sets member x to arg), and was doing something
like this:

	objPtr->X

instead of

	objPtr->X()

It was perfectly repeatable, and maybe I'll try out the Outside Bug Reporter
now that (as a sort of beta tester) I'm actually allowed/encouraged to
use it.


v   v sssss|| joseph hall                      || 4116 Brewster Drive
 v v s   s || jnh@ecemwl.ncsu.edu (Internet)   || Raleigh, NC  27606
  v   sss  || SP Software/CAD Tool Developer, Mac Hacker and Keyboardist
-----------|| Disclaimer: NCSU may not share my views, but is welcome to.