Timeline for How to document raised exceptions in Delphi? [closed]
Current License: CC BY-SA 2.5
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 1, 2018 at 20:56 | history | closed |
EJoshuaS - Stand with Ukraine TylerH Makyen♦ Mogsdad River |
Opinion-based | |
| Jan 29, 2018 at 23:39 | review | Close votes | |||
| Feb 1, 2018 at 20:56 | |||||
| Feb 14, 2011 at 11:24 | vote | accept | jpfollenius | ||
| Jan 31, 2011 at 7:38 | comment | added | jpfollenius | @Barry: There might be several reasons (1) Maybe I want to catch an exception and throw another one (more appropriate one) (2) I might want to show different error dialogs to the user (or no error dialog depending on the context). I'm not talking about unexpected exceptions like access violations and the kind. | |
| Jan 29, 2011 at 20:38 | answer | added | Turin | timeline score: 0 | |
| Jan 29, 2011 at 9:56 | answer | added | Alin Sfetcu | timeline score: 1 | |
| Jan 28, 2011 at 16:04 | answer | added | Ken White | timeline score: 1 | |
| Jan 28, 2011 at 16:01 | answer | added | Trinidad | timeline score: 4 | |
| Jan 28, 2011 at 15:52 | comment | added | Barry Kelly | Why do you want to know which exceptions might be thrown? It's extremely rare that you should catch exceptions, so the need to know the specific type is similarly rare; meanwhile, you should assume that exceptions could be thrown at almost any point, e.g. range checking, floating point, access violation from nil pointer uses, etc. | |
| Jan 28, 2011 at 14:54 | answer | added | Jeroen Wiert Pluimers | timeline score: 1 | |
| Jan 28, 2011 at 14:52 | answer | added | PA. | timeline score: 1 | |
| Jan 28, 2011 at 14:25 | history | asked | jpfollenius | CC BY-SA 2.5 |