mumble

commit 4f8f0209444672d2c2abc119a6b222da6abab294
parent 95118bc1d9090116cbd2ad5423ae023033d5756f
Author: NunoSempere <nuno.sempere@protonmail.com>
Date:   Sun,  7 May 2023 23:02:28 -0400

stop chasing mallocs

I think for chasing mallocs to be meaningful,
I should have a better model of how every piece
of the code is connected. But that would be difficult
and have required advanced planning,
which I don't feel like doing for this project.

Diffstat:
M
mumble
 | 
0

M
src/mumble.c
 | 
2
+-

2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/mumble b/mumble
Binary files differ.
diff --git a/src/mumble.c b/src/mumble.c
@@ -1064,7 +1064,7 @@ lispval* evaluate_lispval(lispval* l, lispenv* env)
         temp_expression->type = LISPVAL_SEXPR;
         lispval* answer = evaluate_lispval(temp_expression, evaluation_env);
 				// delete_lispval(temp_expression);
-				// delete_lispenv(evaluation_env);
+				destroy_lispenv(evaluation_env);
         // lispval* answer = builtin_eval(f->manipulation, f->env);
         // destroy_lispenv(f->env);
         return answer;