Re: The Case for Rust (in any system)

On 13-09-24 12:24, Aryeh Friedman wrote:
> On Fri, Sep 13, 2024 at 7:59 AM Paul Floyd <paulf2718@gmail.com> wrote:

> 
> Incorrect a pointer by definition points to a memory region of

It's really difficult to follow what you are banging on about. One 
moment it's allocators and the next it's pointers.

> *UNKNOWN* size and it is only the runtime environment that keeps track

I'm well aware of that.

> Malloc is not the *ONLY* way to allocate memory at the system level an

You could also implement your own custom allocator based on mmap.

> Go read CLRS it is a very clear and obvious algorthm the only thing

You mean this bit

"10.3 Implementing pointers and objects
How do we implement pointers and objects in languages that do not 
provide them?"

What is the point. We are discussing languages (C, C++ and Rust) that DO 
have them.

> you have to be careful of is it is not O(1) so you need to time it
> carefully when I do the expanson/contraction instead of just letting
> the runtime environment do it for you.    An extreme case of this
> going very wrong happened in July 1969 here is the transcript:
> 
> 4 06 42 10 CC
> Eagle, Houston. You're GO for landing. Over.

Space cadet?

A-
Paul