Re: usage of do {}

> Just as a side note... this is really a stylistic or idiomatic argument. Precisely right. That once again is a bad example I guess :) It is just dictated by the way all the rest of the error handling is done. For example: sub check_table { my ($dbh, $table) = @_; $table = lc $table;

Re: usage of do {}

Wiggins d'Anconia wrote: > Peter Rabbitson wrote: > [snip] > > Either way there shouldn't be a need for eval unless you have raise > error on, but in that case you should catch the exception with [EMAIL > PROTECTED] > > http://danconia.org > > >>Thanks for the feedback >> >>Peter >> > > Ju

Re: usage of do {}

Peter Rabbitson wrote: > On Thu, Jun 30, 2005 at 09:05:00AM -0600, Wiggins d'Anconia wrote: > [snip previous round] > > I am sorry, I wasn't clear enough. I am aware of eval returning the last > statements return value, thus the possibility of having an undef result. > I am using it exclusive

Re: usage of do {}

On Thu, Jun 30, 2005 at 09:05:00AM -0600, Wiggins d'Anconia wrote: > Peter Rabbitson wrote: > > Hello everyone, > > Here and there on the web I encounter claims that the do {} operator is > > depreciated. However I find it convenient to do things like: > > > > eval { some stuff } or do { some mu

Re: usage of do {}

On 6/30/05, Jay Savage <[EMAIL PROTECTED]> wrote: > Checking for $@, though, is a must no matter what you're using [eval] for. +1 despite my completely missing that omission earlier! -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: usage of do {}

On 6/30/05, Wiggins d'Anconia <[EMAIL PROTECTED]> wrote: > Peter Rabbitson wrote: > > Hello everyone, > > Here and there on the web I encounter claims that the do {} operator is > > depreciated. However I find it convenient to do things like: > > > > eval { some stuff } or do { some multiline error

Re: usage of do {}

Peter Rabbitson wrote: > Hello everyone, > Here and there on the web I encounter claims that the do {} operator is > depreciated. However I find it convenient to do things like: > > eval { some stuff } or do { some multiline error handling }; > > is this a bad practice? > > Thanks > > Peter >

Re: usage of do {}

On 6/30/05, Peter Rabbitson <[EMAIL PROTECTED]> wrote: > Here and there on the web I encounter claims that the do {} operator is > depreciated. However I find it convenient to do things like: > > eval { some stuff } or do { some multiline error handling }; > > is this a bad practice? No, that's