Fulltext results:
- syntax @wiki
- [[doku>entities|pattern file]]. There are three exceptions which do not come from that pattern file: multipl
- reference @script
- features such as a class-based object system, and exceptions. It is designed to harmoniously work together wit
- pk3 @fs
- Doomsday [[version_1_8.6|1.8.6]] introduced some exceptions to these rules. See [[automatic_file_mapping_in_p
- records @script:walkthrough
- <- Exceptions ^ ^ Functions -> ====== Records ====== Records are the foundation of Doomsday Script. Each na
- exceptions @script:walkthrough
- - Statements and compounds ^ ^ Records -> ====== Exceptions ====== ===== Try and catch ===== Like in C++, t... ' keywords are used to begin blocks of code where exceptions can be thrown and processed. If an exception is ... n yet.' catch: print 'Skipped.' ===== Throwing exceptions ===== Exceptions are thrown using a ''throw'' statement. * When given one argument, a new exception is thr
- statements_and_compounds @script:walkthrough
- <- Operator expressions ^ ^ Exceptions -> ====== Statements and compounds ====== ===== Structure ===== Stat
- detailed_list_of_changes_in_doomsday_version_1.9.9 @version
- entries). * Correctly handle error situations (exceptions) occuring in worker threads. * Toggling from f
- developer_guidelines @devel
- e should be formatted similarly to C++, with some exceptions. ==== Naming conventions ==== Enumerations, S
- libdeng2_code_guidelines @devel
- mespace de" * error situations are handled via exceptions (see usage of DENG2_ERROR, DENG2_SUB_ERROR through the modules) * error exceptions need to include both function name and the error ... see the existing throws in the code * beware: exceptions cannot be allowed to reach to the libdeng1 one (k
- version_1.2 @snowberry
- ddon folders are read as well. * Fix Snowberry exceptions where the //"C++ part of the ListBox object has b