Support Board
Date/Time: Wed, 14 May 2025 01:37:48 +0000
Post From: Why Software Code Exceptions are Wrong
| [2017-06-02 16:18:44] |
| |
|
There may be the argument, that terminating a program on an exception like a division by zero or access violation makes sense because the program is doing something wrong and it should be halted rather than leaving it in a state where it is doing something potentially seriously wrong. There is no way this can be concluded definitively. These kinds of exceptions do not necessarily indicate that. This argument is not valid because a program can do all kinds of seriously wrong things like using 100 percent of the CPU time of a core on a high priority thread, having a serious memory leak which uses a large amount of system memory and possibly bringing the system to a crawl, or writing to a file endlessly causing a huge amount of disk space to be used and consuming all of the available space. These are very detrimental things a program could do all without triggering an exception. there needs to be a method by which a division by zero or an access violation is signaled and handled, but an abrupt termination is not the proper solution in all cases. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2017-06-03 01:42:33
|