I know about the macro stepper and it doesn't work for my use case. I don't have a simple macro, I have the entire TR typechecker/optimizer. Thus splitting it out into its own module is not feasible. Also because of how TR works there is one major macro application and the macro stepper cannot see into that.
The use case I have is, Take TR program that is being misoptimized, look at the fully expanded syntax and see what went wrong. Thus the thing I need is a good visualization of the fully expanded syntax. The macro stepper may give a slightly more annotated version than 'raco expand' but those annotations are unnecessary for what I need. TR's optimizer is good at using generate-temporary so that you don't need the mark numbers to follow bindings. Also using the macro stepper requires using DrRacket, which has issues when I change its dependencies (TR) out from underneath it and is less keyboard/screen realestate friendly then my terminal. On Thu, Nov 7, 2013 at 9:28 AM, Konrad Hinsen <konrad.hin...@fastmail.net> wrote: > Neil Van Dyke writes: > > > "raco expand"? If you've not yet tried the Macro Stepper feature of > > DrRacket, you are in for a treat. > > And for Emacs fans, Geiser provides macro-expansion-at-a-keypress. > > Konrad. > ____________________ > Racket Users list: > http://lists.racket-lang.org/users ____________________ Racket Users list: http://lists.racket-lang.org/users
