Talk:Exceptions/Catch an exception thrown in a nested call: Difference between revisions

Undo revision 284502 by Paddy3118 (talk)
(Undo revision 284502 by Paddy3118 (talk))
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)
Anonymous user