An optional name of a target to be used as a parent of the current one: - another target of the current system if the attribute `extends_location` is not specified; - a specified target of another system if the attribute `extends_location` is specified; - a library target of another system if this attribute is not specified and the attribute `extends_location` is specified. See also: `extends_location`. An optional location of a system describing a parent target. If specified, the attribute "extends" refers to a target of that system or defaults to the library target, otherwise, the attribute "extends" refers to a target of the current system. See also: `extends`. How should warnings be reported? - none - warnings are not reported; - warning - enabled warnings are reported as warnings; - error - enabled warnings are reported as errors. Is an obsolete iteration syntax used? Obsolete iteration syntax uses "is" with direct access to the iteration item, or uses "as" with direct access to the iteration cursor. When "true", the following obsolete syntax is used: across foo as x loop ... x.item ... x.key ... end across foo is x loop ... x ... @x.key ... end When "false" (the default), the following contemporary syntax is used: across foo as x loop ... x ... @x.key ... end Should a manifest array type be checked against a target type of the reattachment the array is involved in? - mismatch_error - yes, report an error if the types are different; - mismatch_warning - yes, report a warning if the types are different; - standard - no, do not perform any checks specific to manifest arrays. Maximum supported level of cat call detection ordered as follows: - none - no checks; - conformance - conformance checks; - all - complete cat call safety. A CAT-call detection level to be used when an associated target is used as a root. Concurrency values are ordered as follows: - thread - unstructured multithreading, least safe, least restrictions - none - single-threaded applications - scoop - SCOOP, most restrictions Concurrency value to be used when an associated target is used as a root. Maximum supported level of void-safety ordered as follows: - none - no checks; - conformance - conformance checks; - initialization - checks that variables are initialized before use + conformance; - transitional - calls are only allowed on attached expressions + initialization; - all - complete void-safety. A void safety level to be used when an associated target is used as a root. Dead code removal level during finalization: - none - do not remove any code; - feature - remove all features that are reachable neither from the root creation procedure nor from the features marked as visible (this is the default for the previous ECF schemas); - all (default) - same as "feature" plus remove all classes that are not used as targets of object creation and not marked as visible. An override for an option of the same name to control whether a manifest array type should be checked against a target type of the reattachment the array is involved in. The corresponding value can be one of: - default (default) - rely on the option value; - standard - force option value "standard" for all code used in the project; - mismatch_warning - force option value "mismatch_warning" for all code except the code for which the option is set to "standard"; - mismatch_error - force option value "mismatch_error" for all code except the code for which the option is set to "standard". Total order on reals - false - apply IEEE 754 standard rules for comparison of floating point numbers; - true (default) - force total order on floating point numbers, including NaNs. A warning that can be enabled or disabled according to the attribute "enabled". A warning that can be enabled or disabled by the associated attribute "value" taking current date into account. A value that controls when a warning is reported: - none: the warning report is suppressed; - current: the warning is reported only if it is relevant at the time of processing; - all: the warning is reported regarless of the processing time. Void-safety rules to be checked: - none - no rules are checked, this is the only mode without attachment marks at run-time - conformance - attachment status is taken into account in conformance tests - initialization - rules about attribute initialization are checked - transitional - all rules except for object creation with incompletely initialized objects - complete - all rules A mapping of .NET class names of the given namespace into eiffel class names. Processing expectations: - if a class name is listed excplicitly in the attribute `old_name` in one of the renaming elements, it becomes accessible via the name spacified in `new_name` attribute of the renaming element; - otherwise, if the attribute `prefix` is specified, the name of the class is prefixed with the specified string; - otehrwise, no renaming is applied and the class name remains the unchanged. An optional association of the new class name with the old class name. The name of the .NET namespace. An optional prefixed applied to all class names not listed explicitly.