Thanks Alex,
Is the allocated memory purged by the GC in your example? If not, would it
be straightforward to plug it in a manner that the GC handles the free?
Regards,
Kashyap
On Thu, Nov 12, 2020 at 11:21 PM Alexander Burger
wrote:
> Hi Kashyap,
>
> > Could you please share the example where y
Hi Alex,
yes that works with (cons X 1.0), I knew it was a trivial problem.
Thanks!
Cheers
Thorsten
Am Fr., 13. Nov. 2020 um 08:00 Uhr schrieb Alexander Burger <
a...@software-lab.de>:
> Hi Thorsten,
>
> welcome back! :)
>
> > I'm playing around with the native function again (after a long long t
Hi list,
I translated some of the code from Doug Hoyte's Let Over Lambda (Common
Lisp) to PicoLisp.
https://github.com/erdg/lol-picolisp
It implements a lispy version of the FORTH programming language.
Be sure to check out the aw-inspired EXPLAIN.md for a walkthrough of the
code.
WARNING - I t
Hi,
I'm the wrong Alex (and I'm probably wrong), but I would think that memory
allocated by malloc() isn't managed by the GC. IDK if you can install
finalizers or something similar.
Best Regards,
The Other Professor ^W Alex.
Am 13. November 2020 16:30:01 MEZ schrieb C K Kashyap :
>Thanks
Hi Kashyap,
> Is the allocated memory purged by the GC in your example? If not, would it
> be straightforward to plug it in a manner that the GC handles the free?
No, this is not possible. The native call to malloc() is completely unknown to
the Lisp interpreter, and outside the data structures (
Wow Erik,
that's fantastic!
(seems I need to study Doug Hoyte's Let Over Lambda first)
I will dig into it :)
☺/ A!ex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Hi all,
On Fri, Nov 13, 2020 at 06:05:11PM +0100, Alexander Shendi wrote:
> I'm the wrong Alex (and I'm probably wrong),
You are not wrong (in any case ;)
> but I would think that memory allocated by malloc() isn't managed by the GC.
> IDK if you can install finalizers or something similar.
In
Got it! makes sense.
Thanks a lot Alex and Alex :)
On Fri, Nov 13, 2020 at 9:30 AM Alexander Burger
wrote:
> Hi all,
>
> On Fri, Nov 13, 2020 at 06:05:11PM +0100, Alexander Shendi wrote:
> > I'm the wrong Alex (and I'm probably wrong),
>
> You are not wrong (in any case ;)
>
>
> > but I would th
