-
...in .NET version of <e>ROUTINE</e> that may cause an incorrect result or an exception when calling <e>{ROUTINE}.valid_operands</e> on an agent with reference arg
*EiffelStudio: bug#19173 - Fixed a bug that caused an exception when requesting to generate documentation or XMI for a target with a librar
8 KB (1,168 words) - 23:28, 8 July 2016
-
Any I/O operations could raise an exception upon failure.
No I/O operations will raise an exception upon failure.
9 KB (1,447 words) - 04:31, 29 January 2016
-
*Library (Net): Added C functions to use socket functions without raising exception on I/O networking error.
...Web/EWF): Changed the standalone connector implementation to avoid raising exception for any networking error (it brings better debugger experience).
7 KB (1,179 words) - 05:47, 21 March 2017
-
...as their result but then fail to finish their initialization because of an exception.
8 KB (1,214 words) - 01:21, 31 May 2017
-
...ed code generation for old expressions when they are known to not raise an exception.
11 KB (1,663 words) - 03:25, 20 February 2018
-
*library (web): Supported redefinition of the default HTTP response when an exception occurs.
8 KB (1,275 words) - 23:06, 3 September 2018
-
...akpoints, even if assertions are discarded in final mode, to make sure the exception trace uses the same stop point numbers in both final and workbench mode.
*EiffelStudio (diagram): Fixed a bug that might cause an exception when performing multiple switching from an item with an existing diagram to
13 KB (2,009 words) - 02:47, 26 December 2018
-
...est#final045 — Fixed a bug that caused the compiler to terminate with an exception when finalizing code after incremental changes in the buggy source code usi
11 KB (1,666 words) - 08:05, 22 May 2019
