News for hackers. Stuff that matters.
Re:Carp – A statically typed Lisp, without a GC, for real-ti... by DeathArrow on Friday October 15, 2021 @05:24AM (#28875856)
What's the difference between it and Common Lisp? Isn't Common Lisp also AOT compiled?
Re:Carp – A statically typed Lisp, without a GC, for real-ti... by jdc on Friday October 15, 2021 @05:29AM (#28875880)
First of all, Common Lisp is a language with several implementations, some of which offer AOT compilation. Secondly, a garbage-collection (aka automatic memory management) does not exclude AOT.
Re:Carp – A statically typed Lisp, without a GC, for real-ti... by jdc on Friday October 15, 2021 @05:33AM (#28875904)
See also the Boehm GC, a garbage collector for C and C++.

https://en.wikipedia.org/wiki/Boehm_garbage_collector

Re:Carp – A statically typed Lisp, without a GC, for real-ti... by baq on Friday October 15, 2021 @05:25AM (#28875862)
AOT doesn't necessarily mean GC-less, right?
Re:Carp – A statically typed Lisp, without a GC, for real-ti... by brabel on Friday October 15, 2021 @06:52AM (#28876389)
Maybe they actually mean VM-less, which would probably imply GC-less because if you have a GC, you pretty much have a VM doing the GC (unless it's simple ref-count). For embedded, you need VM-less, I think, as VMs tend to be too heavy.
Re:Carp – A statically typed Lisp, without a GC, for real-ti... by bitwize on Friday October 15, 2021 @08:32AM (#28877021)
Gambit has a VM and a GC, and is still AOT-compiled to C. (The Gambit VM is an intermediate representation of Scheme code which is then compiled down to C code.)
Re:Carp – A statically typed Lisp, without a GC, for real-ti... by white-flame on Friday October 15, 2021 @01:50PM (#28880723)
VMs imply a non-native bytecode execution. Garbage collection doesn't require any of that.

It's just normal library code usually called by the allocator, and well-specified memory object/pointer layouts.