🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.std.c
Article #1239

Re: int const * p;

#1239
From: 02-Sep-1992 0949
Date: Wed, 02 Sep 1992 00:50
18 lines
1093 bytes
In article <180188INNmtc@fbi-news.Informatik.Uni-Dortmund.DE> sprave@gonzo.informatik.uni-dortmund.de (Joachim Sprave) writes:
>Could anybody look in the standard, if    int const * p;   is allowed ?

Yes, it would be very easy for you to look that up :-)
(Some parts of the standard are obscure, but not this one.)

>GCC treats it as   const int * p;

That is correct.

>[Other compiler] gives an error.

If the vendor claims that that compiler is ANSI or ISO conforming, and if
you paid money for it, then get a refund.  [Personal opinion only.]
--
Norman Diamond       diamond@jit081.enet.dec.com
If this were the company's opinion, I wouldn't be allowed to post it.
"Yeah -- bad wiring.  That was probably it.  Very bad."
Technical Details
Message-ID: <9209020049.AA12500@enet-gw.pa.dec.com>
Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!jit081.enet.dec.com!diamond

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!jit081.enet.dec.com!diamond
From: diamond@jit081.enet.dec.com (02-Sep-1992 0949)
Newsgroups: comp.std.c
Subject: Re: int const * p;
Message-ID: <9209020049.AA12500@enet-gw.pa.dec.com>
Date: 2 Sep 92 00:50:05 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 18