Talk:Exceptions/Catch an exception thrown in a nested call: Difference between revisions
Content added Content deleted
| Line 2: | Line 2: | ||
Isn't "through nested calls" the normal behavior for [[exceptions]]? What language's exceptions ''doesn't'' work through nested calls? Isn't this basically the same as [[Exceptions]]? --[[User:Spoon!|Spoon!]] 07:01, 7 March 2009 (UTC) |
Isn't "through nested calls" the normal behavior for [[exceptions]]? What language's exceptions ''doesn't'' work through nested calls? Isn't this basically the same as [[Exceptions]]? --[[User:Spoon!|Spoon!]] 07:01, 7 March 2009 (UTC) |
||
:The devils in the detail. For example, some languages might have to annotate each function with details of what exceptions go through them. This example will also point out how one particular exception is caught and not another, that must nevertheless be thrown; and finally the task asks that you describe what happens when a user exception is not caught, languages may give differing amounts of information on the uncaught exception. |
|||
:I did read [[exceptions]], but thought that there was room for another task to bring out other, specific aspects, as well as try and have the examples implement the same thing rather than [[exceptions]] 'show me what you can do' approach. (Which is fine, but different). |
|||
:After my explanation, do you think the task should be deleted? --[[User:Paddy3118|Paddy3118]] 12:50, 7 March 2009 (UTC) |
|||
Revision as of 12:50, 7 March 2009
As opposed to what?
Isn't "through nested calls" the normal behavior for exceptions? What language's exceptions doesn't work through nested calls? Isn't this basically the same as Exceptions? --Spoon! 07:01, 7 March 2009 (UTC)
- The devils in the detail. For example, some languages might have to annotate each function with details of what exceptions go through them. This example will also point out how one particular exception is caught and not another, that must nevertheless be thrown; and finally the task asks that you describe what happens when a user exception is not caught, languages may give differing amounts of information on the uncaught exception.
- I did read exceptions, but thought that there was room for another task to bring out other, specific aspects, as well as try and have the examples implement the same thing rather than exceptions 'show me what you can do' approach. (Which is fine, but different).
- After my explanation, do you think the task should be deleted? --Paddy3118 12:50, 7 March 2009 (UTC)