Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site ki4pv.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!hropus!ki4pv!tanner From: tanner@ki4pv.UUCP (Tanner Andrews) Newsgroups: net.bugs,net.unix-wizards,net.lang.c Subject: Re: weird C-compiler error message Message-ID: <6916@ki4pv.UUCP> Date: Thu, 12-Jun-86 11:41:56 EDT Article-I.D.: ki4pv.6916 Posted: Thu Jun 12 11:41:56 1986 Date-Received: Tue, 17-Jun-86 07:06:12 EDT References: <1297@burl.UUCP> <1926@umcp-cs.UUCP>, <4024@sun.uucp> Organization: CompuData South, DeLand Lines: 16 Xref: watmath net.bugs:818 net.unix-wizards:18389 net.lang.c:9406 ) guy@sun.UUCP writes ) ... if your users are aware that "compiler error" really means "bring this ) message, along with the source code, to your local support person", ... I must take some exception to this. Your local support person is too busy to tell 50 people that "compiler error: gork blunge snarf" means "formal not declared on argument list". For shame! If (when the time comes to decide where in the argument list you found the item to be bound) you can't find it in the argument list, you should make a good effort to emit a useful error. Failing that, publish a list of compiler errors as part of the error list so we know that "gork blunge snarf" means "one of your formal declarations was not on arg list". -- Tanner Andrews