-
*{{Red|base: UNIX_FILE_INFO.update won't raise an exception if the underlying call to `stat' or `lstat' fails (most likely when the fil
9 KB (1,330 words) - 13:05, 6 June 2011
-
...n and it's easier to raise and to track it without inlining given that the exception overhead is high enough anyway.
8 KB (1,214 words) - 23:45, 27 November 2011
-
The only exception is with FILE and DIRECTORY where STRING_8 are interpreted in the current lo
3 KB (516 words) - 16:02, 8 November 2012
-
[[Category:Exception]]
This article documents exception handling mechanisms at implementation level, including runtime and code gen
3 KB (486 words) - 04:17, 21 January 2016
-
* EiffelStudio: bug#16960 - Fixed an exception when showing an inherited class invariant with qualified anchored types (re
5 KB (838 words) - 11:11, 26 November 2013
-
-- Process exception for routines with no Rescue clause.
6 KB (934 words) - 10:20, 1 February 2014
-
...l, above all rule violations. You can double-click on the entry to see the exception details (the call stack, which rule caused it, and so forth).
When an exception occurs while a class is being analyzed the analyzer continues with the next
12 KB (1,957 words) - 15:27, 3 June 2014
-
...rresponding class). In the case an exception is thrown during analysis the exception is caught by the code analyzer and is added to this list. In the graphical
...clause all possible exceptions are caught and recorded. In case of such an exception it then proceeds to the next class.
22 KB (3,657 words) - 15:21, 3 June 2014
-
*compiler: test#anchor079 (related to bug#18893) - Fixed a bug that caused an exception when processing declaration of a qualified anchored type with dependencies
...cursive where if a file cannot be deleted it will exit the routine (via an exception) but would not close the open directory until the GC kicks in.
4 KB (600 words) - 04:53, 3 February 2015
-
*compiler: bug#19120 (test#tuple019) - Fixed a bug that caused a compiler exception when a non-conforming value was assigned to a tuple field.
4 KB (567 words) - 04:07, 26 January 2016
-
...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
