Anonymous user
Talk:Exceptions/Catch an exception thrown in a nested call: Difference between revisions
Talk:Exceptions/Catch an exception thrown in a nested call (view source)
Revision as of 15:47, 25 June 2019
, 4 years ago→11l swallows U1?: Linked.
(→11l swallows U1?: Linked.) |
|||
| (3 intermediate revisions by 2 users not shown) | |||
Line 43:
I think it follows the indicated pattern as long as "call" doesn't have to mean "directly call." Opinions? Is this amount of word mincing acceptable? Should the task description or title be improved? Or do I just worry to much about the details? —[[User:Sonia|Sonia]] 06:44, 30 April 2011 (UTC)
==11l swallows U1?==▼
I can't see what happens to the 11l examples U1 exception when raised? If it is not caught, does it just pass silently? --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 09:10, 25 June 2019 (UTC)▼
:Hi Sonia, A summary of this should be on the task page near the head of your example. You have all the elements here to state what parts of the task description are being stretched; why they need stretching, and how you do it. I don't think that their is a problem with the task ''yet''. You are stretching 'call' to become 'indirectly call' from my interpretation of the above. The task is meant to mean directly call, and the majority - even you I think, have directly call as the normal meaning. I don't want to make the task say directly call as then it might shift the meanong of so much more where I depend on some unwritten shared baseline of meaning. --[[User:Paddy3118|Paddy3118]] 12:34, 30 April 2011 (UTC)
Line 52 ⟶ 49:
:Saw your changes and went and read a bit of the Go faq too. --[[User:Paddy3118|Paddy3118]] 09:10, 2 May 2011 (UTC)
▲==11l swallows U1?==
▲I can't see what happens to the 11l examples U1 exception when raised? If it is not caught, does it just pass silently? --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 09:
: At the present moment the only way of execution of 11l code is to transpile it to C++. So, as in C++ the exact behavior for an uncaught exception in 11l is implementation-defined (for example, MSVC shows an error window [but prints nothing to the console], and GCC prints ‘terminate called after throwing an instance of 'U1'’). --[[User:Alextretyak|Alextretyak]] ([[User talk:Alextretyak|talk]]) 13:39, 25 June 2019 (UTC)
::Thanks, I linked to this explanation. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 15:47, 25 June 2019 (UTC)
| |||