Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!border3.nntp.dca.giganews.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!news.giganews.com.POSTED!not-for-mail NNTP-Posting-Date: Wed, 01 Jun 2011 16:28:53 -0500 From: Pete Becker Organization: Roundhouse Consulting, Ltd. Newsgroups: comp.lang.c++ Date: Wed, 1 Jun 2011 11:28:53 -1000 Message-ID: <2011060111285351246-pete@versatilecodingcom> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: Problem with array objects User-Agent: Unison/2.1.4 Lines: 57 X-Usenet-Provider: http://www.giganews.com X-Trace: sv3-exWy1Y9x4ecLuYbOi8hXC9J25GRh+2hW+ZtyACuEiUGo03HxgqIEizqU062GN7PVHgSJLPlp5TMEErx!wfZQ514GE2wvqg+BJgJsnlI/KZHykHE3epCay2Agj08dG6XD8J4smxBhkZ3lBT9lj1AA9p0= X-Complaints-To: abuse@giganews.com X-DMCA-Notifications: http://www.giganews.com/info/dmca.html 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: 3483 Xref: x330-a1.tempe.blueboxinc.net comp.lang.c++:6020 On 2011-06-01 11:10:50 -1000, Paul said: > "Pete Becker" wrote in message > news:201106011031592971-pete@versatilecodingcom... >> On 2011-06-01 10:22:11 -1000, Paul said: >>> >>> The problem is that people can interpret the standards in different >>> ways, and when the majority of people in a given group come to a >>> consensus about the interpreted meaning, that is the defined meaning. >>> But a technical standard should define what it is written to define , >>> not a clique of people who have a common concencus of its >>> interpretation. >> >> I look forward to seeing your rewrite of the C++ standard with all the >> problems you perceive fixed so that no reader could possibly interpret >> it differently from what you intended. When will it be available? >> > There is no need for this sarcasm, I fully appreciate the mammoth task > of creating the C++ standard. > > But you cannot have it both ways, you want an array to be a non > modifiable object of array type when we discuss pointers to arrays, but > in other situations you want an array to be a sequence of objects. The two are not inherently inconsistent. And when you see potential conflicts in the way things are described you can either proclaim that they are irreconcilable and anyone trying to reconcile them is an idiot, or you can look for a way to read them that makes them consistent; the latter may require accepting an interpretation that's different from your preconceived notions. > Also this object of array type is not clearly defined in the C++ standards. > What exactly is this non modifiable object of array type, is it an > object or is it a type? You're kidding, right? A *non modifiable object* is an object. > > If its an object then , as defined in the standards, an object is a > region of storage, so where is this object stored? Wherever the compiler puts it. > It cannot be stored int he same region as its elements because that > region of storage is modifiable. int arr[5]; int arr0[5]; arr = arr0; // error: arr is not a modifiable object arr[0] = 3; // Ok: array element is modifiable -- Pete Roundhouse Consulting, Ltd. (www.versatilecoding.com) Author of "The Standard C++ Library Extensions: a Tutorial and Reference (www.petebecker.com/tr1book)