Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!ukma!uflorida!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: const in latest draft
Message-ID: <10362@smoke.BRL.MIL>
Date: 5 Jun 89 11:50:25 GMT
References: <16259@gryphon.COM> <10339@smoke.BRL.MIL> <16428@gryphon.COM>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 13

In article <16428@gryphon.COM> sarima@gryphon.COM (Stan Friesen) writes:
>	In the User's Guide to Lattice 3.4, in section 5.3.5, it states:
>"ANSI has reserved 'const' to describe an object that never changes *within*
>*the* *module* that declares it as 'const',...".

I think the first problem is that this is an over-simplified description
of what the semantics of the "const" type qualifier.

Perhaps Lattice's interpretation was a consequence of the admittedly
confusing specification for type qualifiers in earlier drafts of the
standard.

Certainly a non-volatile const object can be allocated to ROM.