Fcalva/cyclone
1
0
Fork 0
mirror of https://github.com/justinethier/cyclone.git synced 2025-05-24 04:25:06 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Beginnings of syntax-rules support

Browse source
This commit is contained in:
Justin Ethier 2016-02-11 22:31:09 -05:00
parent fbb34302dc
commit 65529629d5
1 changed files with 8 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
scheme/cyclone/transforms.sld
View file

@ -752,6 +752,7 @@
;TODO: modify this whole section to use macros:get-env instead of *defined-macros*. macro:get-env becomes the mac-env. any new scopes need to extend that env, and an env parameter needs to be added to (expand). any macros defined with define-syntax use that env as their mac-env (how to store that)? ;TODO: modify this whole section to use macros:get-env instead of *defined-macros*. macro:get-env becomes the mac-env. any new scopes need to extend that env, and an env parameter needs to be added to (expand). any macros defined with define-syntax use that env as their mac-env (how to store that)?
; expand : exp -> exp ; expand : exp -> exp
(define (expand exp env) (define (expand exp env)
;(trace:error `(expand ,exp))
(cond (cond
((const? exp) exp) ((const? exp) exp)
((prim? exp) exp) ((prim? exp) exp)
@ -789,6 +790,12 @@
(let* ((name (cadr exp)) (let* ((name (cadr exp))
(trans (caddr exp)) (trans (caddr exp))
(body (cadr trans))) (body (cadr trans)))
(cond
((tagged-list? 'syntax-rules trans) ;; TODO: what if syntax-rules is renamed?
(expand
`(define-syntax ,name ,(expand trans env))
env))
(else
(set! *defined-macros* (cons (cons name body) *defined-macros*)) (set! *defined-macros* (cons (cons name body) *defined-macros*))
;; Keep track of macros added during compilation. ;; Keep track of macros added during compilation.
;; Previous list should eventually go away once macros are ;; Previous list should eventually go away once macros are
@ -805,7 +812,7 @@
;; - no, we need to do this here so code is carried though all transforms ;; - no, we need to do this here so code is carried though all transforms
;; (alpha, cps, closure, etc). otherwise code has to be interpreted during expansion ;; (alpha, cps, closure, etc). otherwise code has to be interpreted during expansion
;; ;;
`(define ,name ,(expand body env)))) `(define ,name ,(expand body env))))))
((define-c? exp) exp) ((define-c? exp) exp)
((symbol? (car exp)) ((symbol? (car exp))
(let ((val (env:lookup (car exp) env #f))) (let ((val (env:lookup (car exp) env #f)))