Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!tudelft.nl!txtfeed1.tudelft.nl!multikabel.net!newsfeed10.multikabel.net!xlned.com!feeder5.xlned.com!feeder3.cambriumusenet.nl!feed.tweaknews.nl!209.197.12.242.MISMATCH!nx01.iad01.newshosting.com!newshosting.com!216.196.98.144.MISMATCH!border3.nntp.dca.giganews.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: Tue, 22 Nov 2011 00:49:59 -0600 Message-ID: <4ECB4616.5D3E@mindspring.com> Date: Tue, 22 Nov 2011 01:49:58 -0500 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: Size of an arraylist in bytes References: <4ec97cb2$0$289$14726298@news.sunsite.dk> <88mdneGuVukoHlTTnZ2dnUVZ_jGdnZ2d@earthlink.com> <4ECAD480.5FD5@mindspring.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 30 X-Usenet-Provider: http://www.giganews.com NNTP-Posting-Host: 4.154.223.80 X-Trace: sv3-P8Yi81IcSEp7Z5/HchcYYrEIXeWOERoa3KII0IaHp4YupT2EwpYeXcnGOzoI89yVid6a8pFNBBCqRav!f97wnTp0mdj6cykO5XOPFXwhO/7vFRYdTK9rLHISL4QZosw8CrEHidiav6XFPxV0mmjBzwJbc9yF!b/n4UXfh4A== 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: 2354 Xref: x330-a1.tempe.blueboxinc.net comp.lang.c:13766 Ark wrote: > > On 11/21/2011 5:45 PM, pete wrote: > > A null pointer constant, may be converted to null pointer. > > > > I refer to any expression of any type, > > as an instance of that type. > > > > (0.0) is a double. > > > I wonder if an expression > (i.e. a critter with a type and a value) is in > some sense "an instance". > Is there any point in distinguishing an > instance and an object? If so, what is it? The assignment expression statement a = 0; implies that there is an object named (a) and that after the assignment that (a) will have a value of (0). The assignment expression (a = 0) does *not* imply that prior to the assignment that there is a region of storage with a value of (0) waiting to be loaded and moved into (a). -- pete