Deutsch English Français Italiano |
<v6c298$3tko2$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: James Kuyper <jameskuyper@alumni.caltech.edu> Newsgroups: comp.lang.c Subject: =?UTF-8?Q?Re=3A_technology_discussion_=E2=86=92_does_the_world_need?= =?UTF-8?B?IGEgIm5ldyIgQyA/?= Date: Sat, 6 Jul 2024 14:26:47 -0400 Organization: A noiseless patient Spider Lines: 23 Message-ID: <v6c298$3tko2$1@dont-email.me> References: <v66eci$2qeee$1@dont-email.me> <v67gt1$2vq6a$2@dont-email.me> <v687h2$36i6p$1@dont-email.me> <871q48w98e.fsf@nosuchdomain.example.com> <v68dsm$37sg2$1@dont-email.me> <87wmlzvfqp.fsf@nosuchdomain.example.com> <v6ard1$3ngh6$4@dont-email.me> <v6b0jv$3nnt6$1@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Injection-Date: Sat, 06 Jul 2024 20:26:48 +0200 (CEST) Injection-Info: dont-email.me; posting-host="2f8b04a7cbca5d04ee14b3b75be7b597"; logging-data="4117250"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18aEyP8pFFpWMWGnWvrm/JPbxhuLBvbVtk=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:IJ1GtIzS9edF9/qG76xIWkKMir8= Content-Language: en-US In-Reply-To: <v6b0jv$3nnt6$1@dont-email.me> Bytes: 2452 On 7/6/24 04:51, BGB wrote: .... > Yeah, and in the 1D case, an array can be seen as functionally an > implicitly defined pointer with an assigned size and preassigned > backing memory. > > Granted, C generally allows one to see the backing memory, but not the > implicit pointer to said backing memory. I guess one could argue that > if one can't take the address of it, it doesn't exist, but yeah... C won't let you take that pointer's address because it need not exist, and in my experience, usually doesn't. Compilers that I'm familiar with often store all objects that are local to given scope in a single block of memory whose starting address is stored in a register. No memory is set aside to store separate pointer objects pointing to any of those individual objects. When a pointer value pointing at one of those objects is needed, a fixed offset is added to the address stored in that register. Are you familiar with any compilers that handle such things differently? I make no claim to wide knowledge of compilers, but the compilers that I used which work that way are among the most widely used C compilers.