I'm reading a log of requests and responses, and sometimes one request
will be generated and processed in the course of processing another
one. I thought I was fine with using OUTSIDE to skip the generated
request, but then it turned out that *it* might be interrupted by
another one. It gets a little more complicated because the requests
might complete in any order:
Request 5 ID
details
Request 32 ID
details
Request 32 ID
details
Response 5
Response 32
Response 32
In the case at hand, there are never any more details after the
generated request, so I can just skip to *any* response, and then
discard the responses I don't want:
... | notinside "Request 32" "Response"
| strnfind "Request 32"
| strnfind "Response 32"
| ...
But how about the more general case? This seems like something that
must have been done plenty of times, say, in analyzing Do ... End
nesting in programs. I suppose I could keep the nesting level in a
counter in SPECS fairly simply, but I wonder if I'm overlooking some
easier way to deal with it.
¬R