Re: Using strings as immediate char

Article View: net.lang.c

Article #9194

#9194

From: karl
Date: Sun, 24 Aug 1986 19:59

16 lines
1225 bytes

sun!guy (Guy Harris) writes:
>(The real test, of course, is whether
>        cmdchr = menu_selection["rofq"];
>yields the same result.  Any compiler that doesn't produce object code that
>yields the same result isn't a C compiler.)

True, and still true in ANSI C, though I'm still not sure why.  Is there any
valid reason for writing such a mess?  I think it ought to be deprecated, or
even completely illegal (but available, of course, as a "common extension" on
"some compilers").

No, not just for aesthetic reasons.  It makes it easier to define arrays as a
real datatype in future implementations if "x[y]" is redefined slightly.

Karl W. Z. Heuer (ihnp4!ima!haddock!karl), The Walking Lint

Technical Details

Message-ID: <86900026@haddock>

Path: arc1-ca.pugleaf.net!utzoo!mnetor!seismo!think!ima!haddock!karl

References: <6309@sun.uucp>

Show Full Headers

Complete Article Headers

Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: arc1-ca.pugleaf.net!utzoo!mnetor!seismo!think!ima!haddock!karl
From: karl@haddock
Newsgroups: net.lang.c
Subject: Re: Using strings as immediate char
Message-ID: <86900026@haddock>
Date: Sun, 24-Aug-86 15:59:00 EDT
Article-I.D.: haddock.86900026
Posted: Sun Aug 24 15:59:00 1986
Date-Received: Sun, 24-Aug-86 19:49:26 EDT
References: <6309@sun.uucp>
Lines: 16
Nf-ID: #R:sun.uucp:6309:haddock:86900026:000:697
Nf-From: haddock!karl    Aug 24 15:59:00 1986

Reply to Parent Message