Article View: comp.lang.objective-c
Article #144Re: Objective-C and compilation errors messages
From: Lee Sailer
Date: Mon, 29 Oct 1990 16:01
Date: Mon, 29 Oct 1990 16:01
21 lines
1137 bytes
1137 bytes
In article <20850002@hpgnd.HP.COM>, bordes@hpgnd.HP.COM (Olivier BORDES) says:
>or message like ...
> "expected ) found toto."
>... this message appears after a declaration like:
> toto * pointer;
>and means that the type toto has not been declared before !
>Could'nt the compiler say that the type 'toto' has not been defined
>before ?
The "right" way to handle this is for the ID of the error message to
be listed in an error message manual. There should be a discussion, perhaps
even a fairly long one, of all of the ways that programmers screw up
that produce that particular message.
Better yet, this "manual" that explains all the ways to produce a
particular message should be online.
lee
Technical Details
Message-ID:
<90302.110141UH2@psuvm.psu.edu>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!know!sdd.hp.com!wuarchive!psuvax1!psuvm!uh2References:
<20850002@hpgnd.HP.COM>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!know!sdd.hp.com!wuarchive!psuvax1!psuvm!uh2 From: UH2@psuvm.psu.edu (Lee Sailer) Newsgroups: comp.lang.objective-c Subject: Re: Objective-C and compilation errors messages Message-ID: <90302.110141UH2@psuvm.psu.edu> Date: 29 Oct 90 16:01:41 GMT References: <20850002@hpgnd.HP.COM> Organization: Penn State University Lines: 21