Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: BGB <cr88192@gmail.com>
Newsgroups: comp.lang.c
Subject: =?UTF-8?Q?Re=3A_technology_discussion_=E2=86=92_does_the_world_need?=
 =?UTF-8?B?IGEgIm5ldyIgQyA/?=
Date: Sun, 7 Jul 2024 15:10:51 -0500
Organization: A noiseless patient Spider
Lines: 34
Message-ID: <v6esqm$fian$2@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>
 <87h6d2uox5.fsf@nosuchdomain.example.com> <v6d779$6rk5$2@dont-email.me>
 <v6e76u$c0i9$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 07 Jul 2024 22:12:07 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="f7c16b2fffd87ab0346ebf4c8e11259c";
	logging-data="510295"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/KsXONtrQFIvBoE0MW1eQYqNMVspD9y6Y="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:zP+lhrmslkkrlavIG6mku2yxPMY=
Content-Language: en-US
In-Reply-To: <v6e76u$c0i9$1@dont-email.me>
Bytes: 2726

On 7/7/2024 9:03 AM, James Kuyper wrote:
> On 7/7/24 00:55, BGB wrote:
>> On 7/6/2024 5:38 PM, Keith Thompson wrote:
> ...
>>> No, there is no implicitly defined pointer.
> ...
>> This implicit pointer need not exist at a location in memory...
> 
> Which is why C doesn't give you access to it's location in memory -
> something you complained about earlier.

I don't think I was claiming that one should have direct access to its 
location or value within the language, rather that their existence and 
behaviors could be acknowledged in the language design (for a "not quite 
C" language).

My existing compiler uses such pointers internally, but does not give 
programs the ability to access their contents (as this would basically 
open up a crap storm in the semantics; and there is the "less bad" 
option of "just use pointers").


Well, and potentially, one can argue, that the existence or 
non-existence of such pointers could potentially influence the behavior 
of the program in some edge cases (well, along with things like turning 
large local arrays or structs into implicit memory allocations).

Like, say, an implicit malloc call is still a malloc call...

But alas (seemingly it is a necessary evil absent reserving MB of memory 
for the stack for many programs...).

....