On 7 Apr 2005 21:20:19 GMT, rumours say that Leo Breebaart
<[EMAIL PROTECTED]> might have written:
[Max about Leo]
>> This guys famous in the alternative universe of
>> alt.fan.pratchett.
The little imp stopped moving the memory blocks around as soon as it
heard the distinct click of the name "Br
Leif K-Brooks wrote:
Steve Holden wrote:
I've even used an exception called Continue to overcome an irksome
restriction in the language (you used not to be able to continue a
loop from an except clause).
Out of curiosity, how could you use an exception to do that? I would
think you would need to
Leif K-Brooks wrote:
Steve Holden wrote:
I've even used an exception called Continue to overcome an irksome
restriction in the language (you used not to be able to continue a
loop from an except clause).
Out of curiosity, how could you use an exception to do that? I would
think you would need to
Steve Holden wrote:
I've even used an exception called Continue to overcome an irksome
restriction in the language (you used not to be able to continue a
loop from an except clause).
Out of curiosity, how could you use an exception to do that? I would
think you would need to catch it and then use
Roy Smith wrote:
[...]
I think my code is clearer, but I wouldn't go so far as to say I'm
violently opposed to your code. I save violent opposition for really
important matters like which text editor you use.
+1 QOTW
regards
Steve
--
Steve Holden+1 703 861 4237 +1 800 494 3119
Holden W
Leo Breebaart <[EMAIL PROTECTED]> wrote:
> I've recently become rather fond of using Exceptions in Python to
> signal special conditions that aren't errors, but which I feel
> are better communicated up the call stack via the exception
> mechanism than via e.g. return values.
>
> For instance, I'
On Thu, 07 Apr 2005 15:40:24 -0400, Steve Holden <[EMAIL PROTECTED]> wrote:
>Leo Breebaart wrote:
>> I've recently become rather fond of using Exceptions in Python to
>> signal special conditions that aren't errors, but which I feel
>> are better communicated up the call stack via the exception
>>
Max <[EMAIL PROTECTED]> writes:
> LOOK EVERYONE, it's Leo Breebart. You are the same Leo
> Breebart, right?
Breeb*aa*rt. But otherwise, yeah -- I do frequent more than just
one newsgroup. :-)
> This guys famous in the alternative universe of
> alt.fan.pratchett.
I doubt anybody here cares! Who
In article <[EMAIL PROTECTED]>,
Leo Breebaart <[EMAIL PROTECTED]> wrote:
>
>My question is twofold. First, I know that many programmers are
>violently opposed to using exceptions in this fashion, i.e. for
>anything other than, well, exceptional circumstances. But am I correct
>in thinking that in
Leo Breebaart wrote:
I've recently become rather fond of using Exceptions in Python to
signal special conditions that aren't errors, but which I feel
are better communicated up the call stack via the exception
mechanism than via e.g. return values.
Ummm... yeah, I quite agree.
LOOK EVERYONE, it's L
Le 7 Apr 2005 19:23:21 GMT, Leo Breebaart a écrit :
> I've recently become rather fond of using Exceptions in Python to
> signal special conditions that aren't errors, but which I feel
> are better communicated up the call stack via the exception
> mechanism than via e.g. return values.
>
> For in
Leo Breebaart wrote:
I've recently become rather fond of using Exceptions in Python to
signal special conditions that aren't errors, but which I feel
are better communicated up the call stack via the exception
mechanism than via e.g. return values.
Absolutely.
For instance, I'm thinking of methods
12 matches
Mail list logo
