Path: utzoo!mnetor!uunet!husc6!uwvax!oddjob!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.lang.c
Subject: Re: Help me cast this!: Ultrix 2.x bug
Message-ID: <11433@mimsy.UUCP>
Date: 10 May 88 19:29:12 GMT
References: <294@fedeva.UUCP> <1451@iscuva.ISCS.COM> <11344@mimsy.UUCP> <392@m3.mfci.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 24
Keywords: pointer to array of struct

>>In article <386@m3.mfci.UUCP> root@mfci.UUCP (SuperUser) wrote:
>>>... "type (*)[...]" and "type **" are clearly incompatible types....
>>>However, pcc compilers [without Guy Harris's fix, or equivalent]
>>>don't give a warning, and I was once told that Dennis Ritchie considers
>>>it to be perfectly legal C.

>In article <11371@mimsy.UUCP> I asked:
>>Told by whom?

In article <392@m3.mfci.UUCP> root@mfci.UUCP (SuperUser) answered:
>By Bjarne Stroustrup, whom I assume simply asked him.

Well, at least we have Big Names :-) .  Perhaps Dennis has changed his
mind since then, or maybe we just disagree.

[rest deleted; read the parent article.]

In any case, the draft proposed standard makes `type (*)[N]' and
`type **' different types, and treats &array (where array is declared
with `type array[N]') as a value of type `type (*)[N]', which is the
way root@mfci.UUCP and I both think things should be.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris