Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!weretis.net!feeder4.news.weretis.net!feeder.news-service.com!94.75.214.39.MISMATCH!aioe.org!.POSTED!not-for-mail From: Thomas David Rivers Newsgroups: comp.lang.c++ Subject: Re: Problem with array objects Date: Wed, 01 Jun 2011 16:38:16 -0400 Organization: Aioe.org NNTP Server Lines: 55 Message-ID: <4DE6A338.1060909@dignus.com> References: <4DDD9893.9060502@dignus.com> <4DDE50C0.1080402@dignus.com> <8ktDp.17767$h35.800@newsfe19.ams2> <4DDE9FCD.9050005@dignus.com> <4DDFA87C.9060808@dignus.com> <4DDFF65B.8010007@dignus.com> <21UDp.11231$5C7.1331@newsfe10.ams2> <4DE03514.7080802@dignus.com> <4DE10DA2.9050201@dignus.com> <4DE19579.1060300@dignus.com> <4DE252BD.8060100@dignus.com> <4DE2D8FA.6@dignus.com> <7fPEp.12138$El6.500@newsfe21.ams2> <4DE4F114.9040801@dignus.com> <4DE6453C.7080307@dignus.com> <4DE669DE.2050400@dignus.com> <4DE694FE.20606@dignus.com> NNTP-Posting-Host: 5vmandCOS2XnoG0+Ic8whg.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20061027 X-Accept-Language: en-us, en X-Notice: Filtered by postfilter v. 0.8.2 Xref: x330-a1.tempe.blueboxinc.net comp.lang.c++:6009 Paul wrote: > > "Thomas David Rivers" wrote in message > news:4DE694FE.20606@dignus.com... > >> Paul wrote: >> >>> >>> Well I don't know what definitons you are speaking about. >>> As far as I can tell, the way I see arrays and pointers is the >>> correct way , and it never did me any harm. If the C++ standard has >>> some definiton that suggests a pointer of type pointer-to-X can >>> only ever point to a single X object and nothing else then I would >>> probably ignore the C++ standard and carry on with the opinion that >>> the comittee had all become brian dead idiots, TBH :) >>> >> >> Oh, I'm disappointed to read that. I was hoping we could come to an >> understanding that was rooted in the C/C++ language definitions (the >> standard >> documents) but I suppose I'm not able to explain things in a manner >> that you >> agree with. >> >> I'm afraid I will just have to drop things here. >> >> I wish you the best of luck in everything you do. >> > Ok np . > We can agree to disagree. > But I would still like to know what defintions you refer to. > Please can you quote the defintion from the standard you are referring > to. > I cannot find any defintions that suggest a pointer of type T cannot > point to more than one T. In fact I cannot even finds a defintion of a > pointer in the C++ standards however I can in the C standards, but i > don't know if the C standard is embraced into the C++ standard as part > of the fundamental rules. > The definition of a pointer can be found in section 8.3.1 on page 131 of the 1998 C++ standard (ISO/IEC 14882:1998(E)). Appendix C of that same standard discusses compatibility between the C and C++ languages. Section C.1 the relationship between the programming languages, section C.2 provides something similar for the C runtime library. - Dave Rivers - -- rivers@dignus.com Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com