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.
This commit is contained in:
parent
95118bc1d9
commit
4f8f020944
|
@ -1064,7 +1064,7 @@ lispval* evaluate_lispval(lispval* l, lispenv* env)
|
||||||
temp_expression->type = LISPVAL_SEXPR;
|
temp_expression->type = LISPVAL_SEXPR;
|
||||||
lispval* answer = evaluate_lispval(temp_expression, evaluation_env);
|
lispval* answer = evaluate_lispval(temp_expression, evaluation_env);
|
||||||
// delete_lispval(temp_expression);
|
// delete_lispval(temp_expression);
|
||||||
// delete_lispenv(evaluation_env);
|
destroy_lispenv(evaluation_env);
|
||||||
// lispval* answer = builtin_eval(f->manipulation, f->env);
|
// lispval* answer = builtin_eval(f->manipulation, f->env);
|
||||||
// destroy_lispenv(f->env);
|
// destroy_lispenv(f->env);
|
||||||
return answer;
|
return answer;
|
||||||
|
|
Loading…
Reference in New Issue
Block a user