From:	Erik Max Francis <max AT alcyone DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: char **argv vs. char *argv[]
Date:	Thu, 12 Jun 1997 08:52:02 -0700
Organization:	Alcyone Systems
Message-ID:	<33A01B22.6C1AC64@alcyone.com>
References:	<5ndap9$mgd AT freenet-news DOT carleton DOT ca> <01bc74bd$7df85940$e38033cf AT pentium> <5ngpcv$a6v$3 AT sun1000 DOT pwr DOT wroc DOT pl> <339BFF1F DOT 4897 AT cornell DOT edu>
NNTP-Posting-Host:	newton.alcyone.com
Mime-Version:	1.0
Lines:	19
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

A. Sinan Unur wrote:

> uh-um ... what does that mean? no offense, but where exactly do you get
> the notion that
    ...
> will generate a warning? these types of discussions belong in
> comp.lang.c (and probably they are in the C FAQ.)

He was claiming that the array name of an array argument is not a
modifiable lvalue, which is a different thing.  This in, however,
incorrect.

-- 
       Erik Max Francis, &tSftDotIotE / email / max AT alcyone DOT com
                     Alcyone Systems /   web / http://www.alcyone.com/max/
San Jose, California, United States /  icbm / 37 20 07 N  121 53 38 W
                                   \
     "Covenants without the sword / are but words."
                                 / Camden

- Raw text -