Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!ucbvax!bloom-beacon!eru!hagbard!sunic!ericom!eos.ericsson.se!etxtomp
From: etxtomp@eos.ericsson.se (Tommy Petersson)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: "chip" in SAS C
Message-ID: <1991Jan9.152057.9968@ericsson.se>
Date: 9 Jan 91 15:20:57 GMT
References: <1991Jan8.070945.7475@ux1.cso.uiuc.edu> <12579@hacgate.UUCP> <1991Jan9.040641.5245@ux1.cso.uiuc.edu>
Sender: news@ericsson.se
Reply-To: etxtomp@eos.ericsson.se
Organization: Ericsson Telecom AB
Lines: 27

In article <1991Jan9.040641.5245@ux1.cso.uiuc.edu> lrg7030@uxa.cso.uiuc.edu (Loren  Rittle) writes:
>johnl@SDFSUN1.hac.com (John Lee) writes:
>> The SAS/C error
>> message, "Error 25: modifiable lvalue required", does indeed make sense, but
>> in the same way as "syntax error" and is as helpful.  I'd much prefer
>> something along the lines of "conflicting type modifier" or "storage class
>> conflict."
>
>On second thought, I completely agree with you (although, I still
>think that the error message is a bit more helpful than you do :-).
>But guess what, you can change the error message SAS/C presents to
>you without trying to convice SAS to make the change.  Here's how: Edit
>lc:lcerrs.txt.  Search for `modifiable lvalue required' and change
>to `modifiable lvalue required (conflicting type modifier)' or
>whatever you like.
>

...and just hope that the error message isn't used for anything else that
'modifiable lvalue required' is fuzzy enough for, but 'conflicting type
modifier' may be a plain lie...

>Loren J. Rittle
>--
>``In short, this is the absolute coolest computer device ever invented!''
>                   -Tom Denbo speaking about The VideoToaster by NewTek
>``Think about NewTek's VideoToaster!  Now think about the Amiga!''
>Loren J. Rittle lrg7030@uxa.cso.uiuc.edu