Hi Alex, Quick question - when you mentioned "doubling of space" - perhaps you were talking about systems that can only have WORD aligned pointers - is that correct? Regards, Kashyap
On Wed, Apr 22, 2020 at 6:56 AM Guido Stepken <gstep...@gmail.com> wrote: > Well, we have year 2020, not Dijksra 1978. Even embedded systems have a > MMU and you get "Memory Access Violation", so no pointer rage checks needed > to be handled by CPU any longer. Those formerly needed range checks, eating > up clock cycles, now are deeply sticking in MMU and IOMMU ... Bang! - > Exception! > > Also reading about modern "multi generational garbage collectors" will > explain, why garbage collected (functional, pure OO) languages have kept up > with C/C++ statically machine code. Julia language, sitting on FemtoLisp > JIT engine, in some times even ist faster than C > > Have fun! > > Am Mittwoch, 22. April 2020 schrieb Alexander Burger <a...@software-lab.de > >: > > Hi Geo, > > > >> I think you mean 0xF000 for everything? This is indeed cool! but hmm > does > >> it limit the memory for each data type? > > > > Yes, what Guido writes is nonsense. Fixed-sized address spaces are a > terrible > > solution. Doesn't scale, and is extremely inefficient due to the > necessary > > pointer range checks. > > > > PicoLisp's way is far superior, because the tag bits come "free", they > are > > implicit by the natural pointer alignments. > > > > ☺/ A!ex > > > > -- > > UNSUBSCRIBE: mailto:picolisp@software-labde <picolisp@software-lab.de> > ?subject=Unsubscribe > > > >
