On Tuesday, 13 December 2016 at 00:33:58 UTC, Yuxuan Shui wrote:
On Monday, 12 December 2016 at 22:35:22 UTC, Yuxuan Shui wrote:
On Monday, 12 December 2016 at 22:13:59 UTC, Ali Çehreli wrote:
On 12/12/2016 02:08 PM, Yuxuan Shui wrote:
> [...]
wrote:
>> [...]
Error.bypassedException
>> [...]
me
On Monday, 12 December 2016 at 22:35:22 UTC, Yuxuan Shui wrote:
On Monday, 12 December 2016 at 22:13:59 UTC, Ali Çehreli wrote:
On 12/12/2016 02:08 PM, Yuxuan Shui wrote:
> [...]
wrote:
>> [...]
Error.bypassedException
>> [...]
mechanism,
>> [...]
Error."
>> [...]
Exception,
>> [...]
otherwise
>
On Monday, 12 December 2016 at 22:13:59 UTC, Ali Çehreli wrote:
On 12/12/2016 02:08 PM, Yuxuan Shui wrote:
> [...]
wrote:
>> [...]
Error.bypassedException
>> [...]
mechanism,
>> [...]
Error."
>> [...]
Exception,
>> [...]
otherwise
>> [...]
original
>> [...]
is the Error.
> [...]
Exception to
> [.
On 12/12/2016 02:08 PM, Yuxuan Shui wrote:
> Thanks a lot for the explanation!
>
> On Monday, 12 December 2016 at 22:01:54 UTC, Ali Çehreli wrote:
>> (Note: Looks like there is a bug regarding Error.bypassedException
>> member. Would others please confirm.)
>>
>> On 12/12/2016 01:15 PM, Yuxuan Shu
Thanks a lot for the explanation!
On Monday, 12 December 2016 at 22:01:54 UTC, Ali Çehreli wrote:
(Note: Looks like there is a bug regarding
Error.bypassedException member. Would others please confirm.)
On 12/12/2016 01:15 PM, Yuxuan Shui wrote:
> [...]
that Error
> [...]
vague, and I'm
> [...
(Note: Looks like there is a bug regarding Error.bypassedException
member. Would others please confirm.)
On 12/12/2016 01:15 PM, Yuxuan Shui wrote:
> I read https://dlang.org/spec/statement.html, which told me that Error
> is different in the way it's chained. But that is pretty vague, and I'm
>
I read https://dlang.org/spec/statement.html, which told me that
Error is different in the way it's chained. But that is pretty
vague, and I'm still confused.
Can someone explain that using examples?
Thanks.
On Friday, 13 September 2013 at 23:58:33 UTC, Sean Kelly wrote:
Exception chaining is actually built-in. I did some digging
for an official description, but couldn't find one. Here's a
summary:
If an Exception is thrown when an Exception or Error is already
in flight, it is
s expensive as it can get in exception handling code I
> guess).
Exception chaining is actually built-in. I did some digging for an official
description, but couldn't find one. Here's a summary:
If an Exception is thrown when an Exception or Error is already in flight, it
is
In one of my exception handling blocks, I call some code that
could *also*, potentially throw (it's actually a loop, where each
iteration can throw, but I have to do them *all*, meaning I need
to handle *several* extra exceptions). I'm wondering what the
"correct" way of handling both exception
10 matches
Mail list logo
