Analyzing Scheme source code

[Duncan Mak <duncanmak@gmail.com>]

Hello all,

I'm interested in running an analysis of some Scheme source code,
specifically, I'm looking to find what's defined in each file and what
references each file takes on.

I started writing my own analyzer with the match macro, and it looks
something like this:

(define (process-form form)
  (match form
    (['define [name @args] @body]
     (cons name (map process-form body)))
    (['define name value]
     value)
    (['let [[foo bar] ...] @body]
     (map process-form body))
    (['if test then else]
     (list (process-form test)
           (process-form then)
           (process-form else)))
    ([procedure @args]
     (cons procedure (map process-form args)))))

Thinking a bit more, rather than doing it myself, I thought maybe I could
reuse the existing machinery that's in Kawa already, i.e.
https://www.gnu.org/software/kawa/internals/semantic-analysis.html

I think the trick is to get an instance of a Translator for a particular
file, and then call `rewrite` and possibly inspect the resulting Expression
(which ought to be an instance of a ModuleExp?)

(import (class gnu.expr Language NameLookup)
        (class gnu.kawa.io InPort)
        (class gnu.text Lexer)
        (class kawa.lang Translator))

(define (process-file filename)
  (let ((lang (Language:getDefaultLanguage))
        (lexer (language:getLexer (InPort:openFile filename)
(SourceMessages))))
    (Translator lang lexer:messages  (NameLookup lang))))

What I have above seems to only result in an empty Translator.

What's the right way to set up the environment?


-- 
Duncan.