[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Macros as 1st class objects

From: Tk
Subject: Macros as 1st class objects
Date: Tue, 05 Mar 2019 08:12:33 +0000

How likely is that something likes this,
(define macro2 (module-ref (current-module) 'macro1))

breaks in the future versions of Guile? The docs say this is low-level, so I 
have my suspicions.

I have an application that defines abstract interface modules and specialises 
the names of the functions defined in it in other modules that get initialised 
based on user input. For normal procedures, this works fine. Applying the same 
principle to macros could work with the pattern above, but for that to make 
sense, i'd like to know that a) mechanism is stable to medium-term Guile 
evolution, b) the practice is not frowned upon.


Sent with [ProtonMail]( Secure Email.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]