Difference between revisions of "Documentation/DevGuide/GUI/Exception Handling"

From Apache OpenOffice Wiki
Jump to: navigation, search
m (Robot: Changing Category:Graphical User Interfaces)
m (FINAL VERSION FOR L10N)
 
(One intermediate revision by the same user not shown)
Line 4: Line 4:
 
|NextPage=Documentation/DevGuide/GUI/Dialogs and Controls
 
|NextPage=Documentation/DevGuide/GUI/Dialogs and Controls
 
}}
 
}}
{{DISPLAYTITLE:Exception Handling}}
+
{{Documentation/DevGuideLanguages|Documentation/DevGuide/GUI/{{SUBPAGENAME}}}}
 +
{{DISPLAYTITLE:Exception Handling}}
 
In theory, robust exception handling reacts to all unpredictable situations. In practice, many of these situations can be avoided by preventive runtime behavior or by making sure that the methods defined to raise exceptions are only used in a defined context. In these cases empty exception handling as done in the example code is justifiable.
 
In theory, robust exception handling reacts to all unpredictable situations. In practice, many of these situations can be avoided by preventive runtime behavior or by making sure that the methods defined to raise exceptions are only used in a defined context. In these cases empty exception handling as done in the example code is justifiable.
  
 
{{PDL1}}
 
{{PDL1}}
  
[[Category:Documentation/Developers Guide/Graphical User Interfaces]]
+
[[Category:Documentation/Developer's Guide/Graphical User Interfaces]]

Latest revision as of 13:24, 15 May 2009



In theory, robust exception handling reacts to all unpredictable situations. In practice, many of these situations can be avoided by preventive runtime behavior or by making sure that the methods defined to raise exceptions are only used in a defined context. In these cases empty exception handling as done in the example code is justifiable.

Content on this page is licensed under the Public Documentation License (PDL).
Personal tools
In other languages