Fred Drake wrote:
I'll do that. In particular, I propose:
1. The macro extension feature be associated with a new METAL
attribute, extend-macro. This must be used only in conjunction with
define-macro.
2. The define-macro/use-macro combination will become disallowed once more.
3. The METAL s
On 8/18/05, Shane Hathaway <[EMAIL PROTECTED]> wrote:
> Ok. It takes a while to twist my brain back into a mode that
> understands this stuff. Your solution adds capabilities without taking
> any away. +1.
Cool! Thanks for helping think about this.
> Now that I see this better, I'll retract m
Fred Drake wrote:
On 8/18/05, Shane Hathaway <[EMAIL PROTECTED]> wrote:
My use case for macro extension is as follows: a third party provides a
complex macro I'd like to reuse as a macro, but I want to replace only
certain slots in my macro. I need my macro to offer all of the slots
that the b
On 8/18/05, Shane Hathaway <[EMAIL PROTECTED]> wrote:
> My use case for macro extension is as follows: a third party provides a
> complex macro I'd like to reuse as a macro, but I want to replace only
> certain slots in my macro. I need my macro to offer all of the slots
> that the base macro offe
Fred Drake wrote:
T3 should be filling the slot A defined in T2, and T2 should be filling the
slot A defined in T1; this was not happening when T2 extended T1. If T2 did
not extend T1, but simply used it, this worked as expected. Having this slot
construct behave differently in the case of ma
