ConfigurationParserLibrary - Revision history

Patrickr: /* Retrieval and Storage */

2006-11-09T20:22:21Z

‎Retrieval and Storage

2006-11-09T20:22:12Z

‎Retrieval and Storage

2006-11-09T20:18:20Z

2006-11-06T22:01:48Z

‎CONF_OVERRIDE

2006-11-06T22:01:03Z

‎CONF_CLUSTER

2006-11-06T22:00:36Z

‎CONF_ASSEMBLY

2006-11-06T21:59:54Z

‎CONF_LIBRARY

2006-10-31T22:23:23Z

‎CONF_TARGET

2006-10-31T19:27:13Z

2006-10-30T22:41:16Z

‎Implementation

@@ Line 72: / Line 72: @@
 		end
 </code>
-Importing a ACE file.
+Importing an ACE file.
 <code>[eiffel,n]
 	import_ace (a_file: STRING) is

@@ Line 69: / Line 69: @@
 			if not a_system.store_successful then
 				display_error ("Could not store system in " + a_system.file_name)
 			end
 		end
 </code>

@@ Line 36: / Line 36: @@
 === CONF_OVERRIDE ===
 An override cluster is a normal cluster with the special thing, that classes in here with the same name than other classes override classes in the other cluster.
 == Retrieval and Storage ==

← Older revision		Revision as of 22:01, 6 November 2006
Line 35:		Line 35:

	=== CONF_OVERRIDE ===		=== CONF_OVERRIDE ===
		+	An override cluster is a normal cluster with the special thing, that classes in here with the same name than other classes override classes in the other cluster.

	== Retrieval and Storage ==		== Retrieval and Storage ==

← Older revision		Revision as of 22:01, 6 November 2006
Line 32:		Line 32:

	=== CONF_CLUSTER ===		=== CONF_CLUSTER ===
		+	A CONF_CLUSTER represents a cluster that has actual classes in it.

	=== CONF_OVERRIDE ===		=== CONF_OVERRIDE ===

← Older revision		Revision as of 22:00, 6 November 2006
Line 29:		Line 29:

	=== CONF_ASSEMBLY ===		=== CONF_ASSEMBLY ===
		+	A CONF_ASSEMBLY is very similar to a CONF_LIBRARY. Instead of a library_target there is a CONF_PHYSICAL_ASSEMBLY that all references to the same assembly share.

	=== CONF_CLUSTER ===		=== CONF_CLUSTER ===

← Older revision		Revision as of 21:59, 6 November 2006
Line 26:		Line 26:

	=== CONF_LIBRARY ===		=== CONF_LIBRARY ===
		+	A CONF_LIBRARY node describes the use of a library in an application or another library. Once the configuration has been fully parsed it has a library target. All CONF_LIBRARY nodes for one library point to the same library_target.

	=== CONF_ASSEMBLY ===		=== CONF_ASSEMBLY ===

← Older revision		Revision as of 22:23, 31 October 2006
Line 10:		Line 10:

	=== CONF_TARGET ===		=== CONF_TARGET ===
		+	The target is the basic block that an application or a library is built of. A target can extend another target. If a system can be used as a library, one target has to be specified as the library target.
		+
		+	==== Implementation ====
		+	In a fully parsed system, every CONF_SYSTEM has the application_target set. This is the back link in libraries to the target that represents the application.
		+
		+	One thing to take into account when extending another target is, that only classes in clusters/libraries in a target can be reached.
		+	e.g.
		+
		+	*target common
		+	**cluster a
		+	*target special extends common
		+	**cluster b
		+
		+	If we compile target special, classes in b can use classes in a but classes in a can not use classes in b as this is not in the scope of a.

	=== CONF_LIBRARY ===		=== CONF_LIBRARY ===

← Older revision		Revision as of 19:27, 31 October 2006
Line 1:		Line 1:
		+	[[Category:Configuration]]
	== General==		== General==
	The basic layout of a configuration system is a system that has multiple targets (which may inherit from each other), every target can have some libraries, assemblies override clusters and normal clusters. Clusters can have sub clusters.		The basic layout of a configuration system is a system that has multiple targets (which may inherit from each other), every target can have some libraries, assemblies override clusters and normal clusters. Clusters can have sub clusters.

← Older revision		Revision as of 22:41, 30 October 2006
Line 6:		Line 6:

	==== Implementation ====		==== Implementation ====
		+	Every CONF_SYSTEM has an associated UUID. If there is no UUID specified in the configuration file a random one will be generated when the file is loaded. If a system is used as a library the UUID has to be specified in the configuration file as this is used to detect multiple usage of the same library.

	=== CONF_TARGET ===		=== CONF_TARGET ===