# from Michael G Schwern on Monday 24 October 2011 22:12:
>Plan A...
>2) The old one is squirreled away in a stack.
>3) The new handler is told how deeply it's nested.
>...On the down side, every handler needs a delegator ... yucky. ...
>
>Plan B... when a subtest_start happens...
>
>1) An event h
On 2011.10.25 12:29 AM, Eric Wilhelm wrote:
> I like the sound of plan B, except for the "stores itself in" combined
> with "swap me out".
Any specific doubts?
> Can the event coordinator keep a stack? At the point where the parent
> handler has to tell the coordinator "swap me out", you coul
I keep looking at subtests and keeping thinking that if there wasn't a test
count to manage, would we need subtests? Do we need all that complexity? If
it's just about the test count, can it be managed a better way?
I understand wanting "blocks of tests" and the ability to make plans for just
th
# from Michael G Schwern
# on Tuesday 25 October 2011 12:57:
>On 2011.10.25 12:29 AM, Eric Wilhelm wrote:
>> I like the sound of plan B, except for the "stores itself in"
>> combined with "swap me out".
>
>Any specific doubts?
I'm only working from intuition and my understanding of what you
desc
