.NET Namespace Generation - Revision history

Manus at 18:39, 19 March 2007

2007-03-19T18:39:09Z

2007-03-19T18:28:27Z

‎Mixing With Libraries

2007-03-19T18:24:48Z

‎Mixing With Libraries

2007-03-19T18:21:16Z

2007-03-19T18:20:56Z

‎Mixing With Libraries

2007-03-19T18:19:19Z

‎List of Settings

2007-03-19T18:09:33Z

2007-03-19T17:45:30Z

Initial

New page

[[Category:Eiffel for .NET]]
==List of Settings==

==Mixing With Libraries==

==Samples==

@@ Line 15: / Line 15: @@
 # Use Cluster Name as Namespace ('''UCNN'''): If specified, cluster name will be part of the namespace.
 # Use Recursive Cluster Name as Namespace ('''URCNN'''): If specified, then the path to the class will be part of the namespace.
-To make things clearer here is all the possible combinations and their results:
+To make things clearer here is all the possible combinations for the first three options and their results:
 # '''NN''' set to N: N.A, N.B and N.C
 # '''UCNN''' set to True: root.A, root.B and root.C

@@ Line 40: / Line 40: @@
 ==Mixing With Libraries==
-Once options are set at a library level, they cannot be overridden. The compiler will use the library settings to generate the namespaces.
+Once options are set at a library level, they cannot be overridden. The compiler will use the library settings to generate the namespaces. This is why the option is non-functioning/disallowed for library, precompile or assembly nodes in the configuration file.
 ===Why?===

← Older revision		Revision as of 18:24, 19 March 2007
Line 41:		Line 41:
	==Mixing With Libraries==		==Mixing With Libraries==
	Once options are set at a library level, they cannot be overridden. The compiler will use the library settings to generate the namespaces.		Once options are set at a library level, they cannot be overridden. The compiler will use the library settings to generate the namespaces.
		+
		+	===Why?===
		+	Suppose we have the following system:
		+	target a
		+	library l1
		+	library l2
		+	library l3
		+
		+	target library l2
		+	library l3
		+
		+	If both target '''a''' and '''library l2''' were to specify a different namespace, it would be hard to know which one should take precedence. Let's assume it is '''a''', then if library '''l2''' relies on a certain namespace for '''l3''' then library '''l2''' might stop working properly, which would be bad.

← Older revision		Revision as of 18:21, 19 March 2007
Line 41:		Line 41:
	==Mixing With Libraries==		==Mixing With Libraries==
	Once options are set at a library level, they cannot be overridden. The compiler will use the library settings to generate the namespaces.		Once options are set at a library level, they cannot be overridden. The compiler will use the library settings to generate the namespaces.
−
−	~~==Samples==~~

← Older revision		Revision as of 18:20, 19 March 2007
Line 40:		Line 40:

	==Mixing With Libraries==		==Mixing With Libraries==
		+	Once options are set at a library level, they cannot be overridden. The compiler will use the library settings to generate the namespaces.

	==Samples==		==Samples==

@@ Line 10: / Line 10: @@
 ==List of Settings==
-*At the target level you can specify the following:
+===Target options===
 # .NET Namespace ('''NN'''): Namespace in which all classes will be put in.
 # Use Cluster Name as Namespace ('''UCNN'''): If specified, cluster name will be part of the namespace.
@@ Line 25: / Line 26: @@
 ### '''UCNN''' and '''URCNN''' set to True: N.root.A, N.root.d1.B and N.root.d2.C
 ==Mixing With Libraries==
 ==Samples==