Path: utzoo!utgpu!attcan!uunet!husc6!uwvax!umn-d-ub!umn-cs!ns!ddb
From: ddb@ns.UUCP (David Dyer-Bennet)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Great Moments In Error Messages -- Microsoft C 5.1
Message-ID: <726@ns.UUCP>
Date: 8 Aug 88 19:15:45 GMT
References: <335@optilink.UUCP> <769@euraiv1.UUCP>
Organization: Network Systems Corp. Mpls MN
Lines: 20

In article <769@euraiv1.UUCP>, evas@euraiv1.UUCP (Eelco van Asperen) writes:
> 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; 
   I have to disagree.  It may be _inevitable_ behavior given, as you say,
that msc stores the text of error messages in external files, and couldn't
get at them because the error message was due to running out of open
file slots;  but I can't bring myself to call it sensible!
   Actually, I think that the error messages for things precluding openning
the error message files should be hardcoded, to prevent precisely this
situation.  Yes, I realize that that makes them come out in the wrong
language in most countries in the world, but that's better than nothing.
   Also, I believe the original post said that C1015 wasn't listed in
the manual, which is an apalling botch.
-- 
	-- David Dyer-Bennet
	...!{rutgers!dayton | amdahl!ems | uunet!rosevax}!umn-cs!ns!ddb
	ddb@Lynx.MN.Org, ...{amdahl,hpda}!bungia!viper!ddb
	Fidonet 1:282/341.0, (612) 721-8967 hst/2400/1200/300