[gambit-list] Figuring out opaque:, and macros expanding to macros
feeley at iro.umontreal.ca
Tue Apr 15 10:57:06 EDT 2014
On Apr 15, 2014, at 9:59 AM, Álvaro Castro-Castilla <alvaro.castro.castilla at gmail.com> wrote:
> I've been figuring out all the attributes available with define-type in Gambit. Testing and thanks to:
> I could understand all but one: opaque. The ways to "learn" how things work with macros producing code is generally the trick (pp (lambda () (macro...)) 'asdf). But what about macros that produce macros? In that case you get an empty form with 'asdf, so no way to know what has been generated.
> That of course applies to define-type. There is no difference in generated code with opaque: keyword, so I assume that it only affects non-generative types. Can I see the generated code in such case?
> Reading Gambit's code in nonstd.scm doesn't clarify things either.
> Thank you!
(set! ##define-type-expansion-show? #t)
More information about the Gambit-list