From 9ef1009e1f71d5d567f50e7b595affa5b6298ab0 Mon Sep 17 00:00:00 2001 From: Justin Ethier Date: Tue, 25 Aug 2015 23:29:36 -0400 Subject: [PATCH] Updated TODO's --- TODO | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/TODO b/TODO index 4bf5e169..ea1b7f8d 100644 --- a/TODO +++ b/TODO @@ -20,6 +20,7 @@ Working TODO list. should start creating issues for these to get them out of her - macros - next steps: + - migrate tests from test2.scm to unit-test suite - how should ex rename/compare work? check working implementations, papers. find test cases that cyclone does not handle right now - review 4 cases below for handling macro expansion. I think there are still some outstanding issues with respect to eval'd macros @@ -111,11 +112,8 @@ when it does not have to, and slowing down compilation even more cyclone> (call/cc (lambda (k) (k 1))) Error: Expected 2 arguments but received 1. - - eval - there is limited concept of macro expansion, probably other deficiencies as well - call/cc issues? - almost certainly will break when running the self-hosted compiler... - no, I think this is ok. may want to unify macros with compiler side though + extra 'cont' param is being exposed, because this works: + (call/cc (lambda (k) (k 1 1)) (lambda (k) (k 1 1))) - I/O - may be able to use fmemopen to implement output strings, although it is not supported on windows