Attention is currently required from: laforge, pespin.
1 comment:
Patchset:
> An altstep cannot have a return value […]
The deeper point is that i don't really want to have an altstep that can be integrated into other altsteps, I want these functions to specifically expect a given message within a limited time, so that i get nicer test failure logging without the need to search far and wide which message may have gone missing. For this, a function is better suited than an altstep. If we ever need altsteps too, then we can find a nifty way to reduce code dup, but so far i only want those parts for which functions are suited well.
(altstep inout parameters have nontrivial limitations on the scoping.)
(i don't want to have to start a timer externally whenever calling f_rua_expect(), i want a convenient implicit timer)
To view, visit change 31765. To unsubscribe, or for help writing mail filters, visit settings.