Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!snorkelwacker!mit-eddie!bu.edu!bu-cs!dartvax!eleazar.dartmouth.edu!matthews
From: matthews@eleazar.dartmouth.edu (Jim Matthews)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MPW wish list
Keywords: MPW
Message-ID: <19265@dartvax.Dartmouth.EDU>
Date: 9 Feb 90 16:09:41 GMT
References: <1990Jan23.065751.29303@peace.waikato.ac.nz> <6310@internal.Apple.COM> <55359@hobbit.UUCP> <1990Jan25.191441.26280@oracle.com> <416@dbase.A-T.COM> <19240@dartvax.Dartmouth.EDU> <10865@claris.com>
Sender: news@dartvax.Dartmouth.EDU
Organization: Dartmouth College, Hanover, NH
Lines: 14

In article <10865@claris.com> drc@claris.com (Dennis Cohen) writes:
>I think that a better solution for such simple errors would be one that was
>in one of the first Pascal compilers I ever used (1979). The University of
>Wisconsin's Univac 1100 compiler gave a warning message with the context and
>continued to compile, treating the source as though the semicolon were there.

Mac compilers could go a long way towards being more helpful in dealing
with errors.  My pet peeve is when Think C tells me that a function call
is incompatible with a prototype, without telling me which parameter is
wrong or what type it was expecting.  The compiler has that information,
and it could do much better than issue "wrong, guess again" error messages.

Jim Matthews
Dartmouth Software Development