Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!ames!mailrus!iuvax!pur-ee!j.cc.purdue.edu!nwd
From: nwd@j.cc.purdue.edu (Daniel Lawrence)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Great Moments In Error Messages -- Microsoft C 5.1
Summary: errors in MSC
Keywords: MSC errors
Message-ID: <7541@j.cc.purdue.edu>
Date: 9 Aug 88 13:43:35 GMT
References: <335@optilink.UUCP> <769@euraiv1.UUCP> <726@ns.UUCP>
Reply-To: nwd@j.cc.purdue.edu.UUCP (Daniel Lawrence)
Organization: Purdue University
Lines: 17

> in article <335@optilink.UUCP>, cramer@optilink.UUCP (Clayton Cramer) says:
> >     C1015:
> > Yup!  That's it!  No message -- just a number.  
> This is perfectly sensible behaviour; 

	If MSC opened its error message file FIRST.. this would not be
able to happen.  Errors are something that can occur at any time in a
program... and MSC should make sure it can report them properly at any
time.

	Messages could also be hard coded without an error file by using
a header file with definitions for the messages (which could be changed
for different languages).

			Daniel Lawrence		(317) 742-5153
			UUCP:	{ihnp4!pur-ee!}j.cc.purdue.edu!nwd
			ARPA:	nwd@j.cc.purdue.edu
			FIDO:	1:201/2 The Programmer's Room (317) 742-5533