15:28 <rick42> hello peeps

15:29 <Regenaxer> Hi rick42!

15:29 <rick42> Hey Regenaxer! :)

15:30 <Regenaxer> ☺

15:55 <CORDIC> Hi Regenaxer, rick42.

15:56 <CORDIC> Should We reply to GC question on the Mailing List that PicoLisp implementation's Source Code should be it's Configuration like Suckless.org.

16:01 <rick42> yeah, i thought Regenaxer would be the only one who could answer. i only know what i've heard Regenaxer say: something like "picolisp pre-allocates the heap at runtime start and then manages 'allocations' of cells in there manually (i.e. part of the picolisp VM machinations)"

16:02 <rick42> so, how could that help this guy? i'm not sure. maybe if s/he learns how it's done then her/his own manual management is already halfway done.

16:04 <rick42> he*

16:04 <rick42> looks like he's Seteeri on gh: https://github.com/Seteeri

16:06 <rick42> the README of protoform (https://github.com/Seteeri/protoform) says "Protoform moving to PicoLisp", although it's still in CL. nothing else in README about picolisp (like linking to another repo).

16:11 <rick42> looks like he understands more than I thought (definitely more than I do :). https://github.com/Seteeri/picolisp/blob/dev/README.md

16:15 <rick42> under the section heading "Lisp defined", he gives high marks to picolisp for actually being a lisp. I also immediately thought of some extreme kool-aid drinking cll-ers who would view it as flamewar fodder. lol https://github.com/Seteeri/picolisp/blob/dev/README.md#lisp-defined

16:19 <rick42> CORDIC: i thought he was wondering if gc internals could be exposed to the user (in some way or manner) for *runtime* use (as opposed to suckless-like configuration)

16:19 <rick42> maybe i read that wrong

16:20 <rick42> CORDIC: btw you just reminded me of when i used to use dwm and st. :)

16:21 <Regenaxer> Hi CORDIC, rick42! Yes, I planned to answer, but on the road atm

16:22 <rick42> of course. safe travels!

16:22 <Regenaxer> I don't understand why he wants to db some things

16:22 <Regenaxer> well, just walking in the fields ;)

16:22 <rick42> i don't either, but sounds interesting

16:22 <rick42> hehe nice!

16:22 <Regenaxer> yeah

16:22 <rick42> (don't stumble and fall :)

16:23 <Regenaxer> I take care :)I see no reason to have a variable CELLS though

16:23 <Regenaxer> or all this other allocation stuff

16:24 <Regenaxer> My experience is that people worry too early about gc

16:24 <Regenaxer> gc is very fast in pil

16:24 <Regenaxer> can simply be igored

16:24 <Regenaxer> ignored

16:27 <rick42> T, and if this is the case here too, it would be a nice non-toy use case to highlight the applicability of what is already in pil

16:28 <Regenaxer> true

16:28 <rick42> Regenaxer: you are right. more thinking than coding has to be done first :)

16:28 <Regenaxer> :)

17:47 <Regenaxer> Wrote something. Now shower :)

18:30 <rick42> ok. just read it. looks good!

18:35 <Regenaxer> Thanks!