Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.dougwise.org!nntpfeed.proxad.net!proxad.net!feeder1-2.proxad.net!74.125.46.80.MISMATCH!postnews.google.com!news2.google.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.earthlink.com!news.earthlink.com.POSTED!not-for-mail NNTP-Posting-Date: Mon, 27 Jun 2011 00:33:21 -0500 Message-ID: <4E081602.7842@mindspring.com> Date: Mon, 27 Jun 2011 01:32:50 -0400 From: pete Reply-To: pfiland@mindspring.com Organization: PF X-Mailer: Mozilla 3.04Gold (WinNT; I) MIME-Version: 1.0 Newsgroups: comp.lang.c Subject: Re: what about my array type? References: <4e076731$0$44197$4fafbaef@reader1.news.tin.it> <4e0810a9$0$15669$4fafbaef@reader2.news.tin.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 40 X-Usenet-Provider: http://www.giganews.com NNTP-Posting-Host: 4.154.217.214 X-Trace: sv3-R924PSjKDYrxHMjU6HW6VD6880czmhUiNQuhCCKPKmUG4nw37zjl0XJ5+aZhvt2H/RQi+UdNtifgHhD!sPQ7oha/kQ8DUB3/2BcVXJzOTUtPyE7t1hv5wYXFnG+3iv4uIbevsdr558nsgz09D6s4tsxHC8mu!n70Yf0o8JDM= X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 X-Original-Bytes: 2313 Xref: x330-a1.tempe.blueboxinc.net comp.lang.c:7022 io_x wrote: > > "Barry Schwarz" ha scritto nel messaggio > news:t7mf07d716olfv14kqcem0dalkhksue6po@4ax.com... > > On Sun, 26 Jun 2011 19:08:36 +0200, "io_x" wrote: > >>when someone has "a=3" > >>than is possible to have &a, but why not &3? > >>where &3 means the place in the memory [address] > >>where there is stored the value 3 > > > > What makes you think that the value 3 must be stored somewhere in > > memory? > > because here is in the memory, it could be in section data > can be in section text, for example the instruction > mov eax, 3 > has in the code section, in the space reserved for store the memory > for this instruction, has the number 3 > there is one addres in the executable that contai 3 That just happens to be that way on the C implementation that you are using right now. There's no rule in C which specifies how a = 3; must be translated. a = 3; only means that after the statement is executed, that (a) will have a value of 3. If the statement were a = 0; instead, then it might be translated as a (clear) instruction, rather than as a (mov) instuction. -- pete