in reply to Re: "next" from within eval {} ?
in thread "next" from within eval {} ?
In the real code there's further things being done in between the do_*() calls (computations depending on the return values of the functions etc.). So I'm not sure if chaining the calls with && would make it any clearer. (I've heavily simplified the code not to distract too much from my actual question about the reasoning behind the warning.)
I just thought that putting one eval around that entire code block would save me from having to clutter up the code with multiple evals with separate identical "catch" clauses. etc., but the warning made me wonder if there's anything wrong with it...
Thanks.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^3: "next" from within eval {} ?
by BrowserUk (Patriarch) on Dec 15, 2011 at 17:12 UTC | |
by Anonymous Monk on Dec 15, 2011 at 17:32 UTC | |
by BrowserUk (Patriarch) on Dec 15, 2011 at 17:49 UTC |