On Tuesday 09 September 2008 15:10:13 Michael G Schwern wrote: > The goal of the test seems to be to detect that a customized caller() > routine is not blown away by Sub::Uplevel. A much safer way to do that is > to have your customized caller() just flick a file-scoped variable when it > gets called and look for that change.
That sounds relatively thread unsafe (or have I written too much C code lately?). -- c