ConfigurationOptions - Revision history

Patrickr at 19:49, 30 October 2006

2006-10-30T19:49:39Z

2006-10-25T00:48:52Z

Reformatted and specified wanted solution # 1

2006-10-16T18:36:57Z

‎Library approach

2006-10-16T18:30:23Z

‎Library approach

2006-10-16T18:06:09Z

‎Application approach

2006-10-16T18:04:21Z

2006-10-14T00:19:14Z

‎Example

2006-10-14T00:08:34Z

2006-10-14T00:08:05Z

2006-10-14T00:06:22Z

@@ Line 15: / Line 15: @@
 == Problem ==
-Should option values be specified in a library or in a project that uses the library? Below we describe the two possible solutions. Currently we aim at Solution number 1 "Library approach".
+Should option values be specified in a library or in a project that uses the library? Below we describe the two possible solutions. The implemented solution is number 1 "Library approach".
 == Solution 1: Library approach ==

@@ Line 15: / Line 15: @@
 == Problem ==
-Should option values be specified in a library or in a project that uses the library?
+Should option values be specified in a library or in a project that uses the library? Below we describe the two possible solutions. Currently we aim at Solution number 1 "Library approach".
-== Solutions ==
+== Solution 1: Library approach ==
-=== Library approach ===
 A library is a black box and therefore everything is specified in the library. Usual settings could be
 * read only
@@ Line 29: / Line 28: @@
 * on libraries directly included in the application we can specify option values (or alternatively set a flag that specifies to use the application options) directly in the library group that includes the library
-=== Application approach ===
+== Solution 2: Application approach ==
 An application should have full control, therefore we use values specified in the application. A common scenario could be that a user has a library which he uses in another application and the testing of the library is done by using it in the application, therefore all warnings should be reported, debugs, trace, profile could be enabled, assertion level may be higher.
-== Example ==
+== Example for various solutions ==
 [[Image:Config example.png]]

@@ Line 27: / Line 27: @@
 ==== Overriding values ====
-* on libraries directly included in the application we can specify option values directly in the library group that includes the library
+* on libraries directly included in the application we can specify option values (or alternatively set a flag that specifies to use the application options) directly in the library group that includes the library
 === Application approach ===

@@ Line 38: / Line 38: @@
 === Library approach ===
-Base, vision2, wel set the options and those options are used. The options of base and vision2 can be overridden (but they have to be overridden for each library separately), wel can not be overridden (unless it would be included in the application directly).
+Base, vision2, wel set the options and those options are used. The options of base and vision2 can be overridden (but they have to be overridden for each library separately), wel can not be overridden (unless it is included in the application directly).
 === Application approach ===
 All the options are specified in ES, it's possible to specify specific values for the used libraries that are directly included, otherwise the default values from the application will be taken.

← Older revision		Revision as of 18:06, 16 October 2006
Line 41:		Line 41:

	=== Application approach ===		=== Application approach ===
−	All the options are specified in ES, it's possible to specify specific values for the used libraries, otherwise the default values from the application will be taken.	+	All the options are specified in ES, it's possible to specify specific values for the used libraries that are directly included, otherwise the default values from the application will be taken.

← Older revision		Revision as of 00:19, 14 October 2006
Line 36:		Line 36:

	Simplified configuration system of the compiler. ES is EiffelStudio (the application), vision2 is the graphic library used by ES which internally uses WEL. The application and all libraries use base.		Simplified configuration system of the compiler. ES is EiffelStudio (the application), vision2 is the graphic library used by ES which internally uses WEL. The application and all libraries use base.
		+
		+	=== Library approach ===
		+	Base, vision2, wel set the options and those options are used. The options of base and vision2 can be overridden (but they have to be overridden for each library separately), wel can not be overridden (unless it would be included in the application directly).

@@ Line 2: / Line 2: @@
 [[Category:Configuration]]
 Handling of options specified in libraries.
 == Available Options ==
@@ Line 33: / Line 31: @@
 === Application ===
 An application should have full control, therefore we use values specified in the application. A common scenario could be that a user has a library which he uses in another application and the testing of the library is done by using it in the application, therefore all warnings should be reported, debugs, trace, profile could be enabled, assertion level may be higher.