From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10ad19,23963231b5359f74 X-Google-Attributes: gid10ad19,public X-Google-Thread: 103376,23963231b5359f74 X-Google-Attributes: gid103376,public X-Google-Thread: 1073c2,23963231b5359f74 X-Google-Attributes: gid1073c2,public X-Google-Thread: 101deb,23963231b5359f74 X-Google-Attributes: gid101deb,public X-Google-Thread: 107a89,23963231b5359f74 X-Google-Attributes: gid107a89,public X-Google-Thread: 11440e,23963231b5359f74 X-Google-Attributes: gid11440e,public X-Google-Thread: 10a146,23963231b5359f74 X-Google-Attributes: gid10a146,public X-Google-ArrivalTime: 2001-06-08 20:52:16 PST Path: archiver1.google.com!newsfeed.google.com!sn-xit-02!supernews.com!nntp-relay.ihug.net!ihug.co.nz!newsfeed.berkeley.edu!ucberkeley!sjc1.nntp.concentric.net!newsfeed.concentric.net!global-news-master From: Patricia Shanahan Newsgroups: comp.lang.ruby,comp.lang.ada,comp.lang.awk,comp.lang.clarion,comp.lang.java.programmer,comp.lang.pl1,comp.lang.vrml Subject: Re: Long names are doom ? Date: 09 Jun 2001 03:51:01 GMT Organization: Concentric Internet Services Message-ID: <3B219DB3.4BF2A68A@acm.org> References: <9f2nks$ibd$0@dosa.alt.net> <3B177EF7.2A2470F4@facilnet.es> <9f8b7b$h0e$1@nh.pace.co.uk> <9f8r0i$lu3$1@nh.pace.co.uk> <9fgagu$6ae$1@nh.pace.co.uk> <9fjgha$blf$1@nh.pace.co.uk> <35mqhtkdfma2rggv1htcaq6vfn2ihs67a1@4ax.com> <9fli1b$4aa$1@nh.pace.co.uk> <3B20E1B0.3EC7FEBB@dresdner-bank.com> NNTP-Posting-Host: 208.36.181.229 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: en Xref: archiver1.google.com comp.lang.ruby:10522 comp.lang.ada:8476 comp.lang.awk:2945 comp.lang.clarion:21522 comp.lang.java.programmer:74954 comp.lang.pl1:946 comp.lang.vrml:3685 Date: 2001-06-09T03:51:01+00:00 List-Id: James Kanze wrote: > > Pete Thompson wrote: > > [...] > > Well, sure. Pointer arithmetic in C/C++ is inherently unsafe and > > encourages obfuscation. However, it also promotes flexibility. > > Just curious, but what can you do with pointer arithmetic in C/C++ > that you couldn't do otherwise, in a cleaner fashion? ... Manage memory. A memory allocator, such as malloc, or the corresponding kernel code, or the code underlying "new", has a split view of memory. It must perform calcuations to determine where to put the the newly created object. It must return a pointer to it. Patricia