On 06/03/2016 07:19 AM, Eric Covener wrote:
Maybe a global directive to turn off the nesting check? Or a convention for the macro name? Or a second tag like <MacroNoNestingCheck> (bad name) that is a very thin wrapper around existing stuff?
Would a MacroOptions (or similar) as the first directive inside a <Macro> block work as a general extension mechanism?
Perhaps it would be too surprising to the end user, since it would be (ideally) swallowed by the macro block instead of replayed.
--Jacob
