Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!blkcat!Uucp
From: Jim.Russell@p395.f421.n109.z1.FidoNet.Org (Jim Russell)
Newsgroups: comp.sys.mac.programmer
Subject: More C+- woes: HELP
Message-ID: <673155029.0@blkcat.FidoNet.Org>
Date: 29 Apr 91 13:20:18 GMT
Sender: Uucp@p0.f40.n109.z1.FidoNet.Org
Lines: 8

LA>      So, following the (very sparse) documentation in the Think C
LA>documentation, I call "myObject::MyMethod(...)".  The result?  The
LA>compiler returns "invalid method call" (or something approximating
LA>that msg).  HUNH?!! 

I was having problems like that, and convinced myself for a while that a call, for example,  of the form inherited::foo could only be made from a method that was itself called foo. Thanks to Philip Keller I was shown that I was wrong, and have since found that most of my "invalid method call" errors were cockpit errors - I failed to #include the CParent.h file, I had a missing ";" or */, etc.  It's one of those things that I have not proved to myself, but they have gone away as I have kept cleaning things 





up.

 * Origin: Gaithersburg, MD (1:109/421.395)