Language Reference/Namespaces - Revision history

Thomas Linder Puls: namespace \

2019-02-26T15:03:42Z

namespace \

← Older revision		Revision as of 17:03, 26 February 2019
Line 9:		Line 9:

	<vipbnf><NamespaceIdentifier>: one of		<vipbnf><NamespaceIdentifier>: one of
			\
	<LowercaseIdentifier>		<LowercaseIdentifier>
	<LowercaseIdentifier> \ <NamespaceIdentifier></vipbnf>		<LowercaseIdentifier> \ <NamespaceIdentifier></vipbnf>

Thomas Linder Puls: /* Open namespaces */ formatting

2012-10-02T10:42:18Z

Open namespaces: formatting

← Older revision		Revision as of 12:42, 2 October 2012
Line 64:		Line 64:

	<OpenQualification>: one of		<OpenQualification>: one of
	open <NamespaceIdentifier> \		open <NamespaceIdentifier>\
	...</vipbnf>		...</vipbnf>

Thomas Linder Puls: Example Template

2008-11-05T10:18:17Z

Example Template

← Older revision		Revision as of 12:18, 5 November 2008
Line 28:		Line 28:
	Any interface, class and implementation that is meet inside a namespace region belongs to that namespace.		Any interface, class and implementation that is meet inside a namespace region belongs to that namespace.

	~~'''~~Example~~'''~~		{{Example\|

	<vip>class aaa		<vip>class aaa
	end class aaa		end class aaa
Line 46:		Line 45:

	Subsequently, the class <vp>aaa</vp> belongs to the root namespace, the class <vp>bbb</vp> belongs to the namespace <vp>xxx</vp> and finally the class <vp>ccc</vp> belongs to the namespace <vp>xxx\yyy</vp>.		Subsequently, the class <vp>aaa</vp> belongs to the root namespace, the class <vp>bbb</vp> belongs to the namespace <vp>xxx</vp> and finally the class <vp>ccc</vp> belongs to the namespace <vp>xxx\yyy</vp>.
			}}

	=== Referencing names in namespaces ===		=== Referencing names in namespaces ===
Line 69:		Line 69:
	Opening a namespace is distinguished from opening a class/interface by a trailing backslash.		Opening a namespace is distinguished from opening a class/interface by a trailing backslash.

	~~'''~~Example~~'''~~		{{Example\|

	<vip>class aaa		<vip>class aaa
	open xxx\yyy\		open xxx\yyy\
Line 77:		Line 76:

	The namespace <vp>xxx\yyy</vp> is opened inside <vp>aaa</vp>.		The namespace <vp>xxx\yyy</vp> is opened inside <vp>aaa</vp>.
			}}

	When a namespace is open that part of a full name can be left out.		When a namespace is open that part of a full name can be left out.

	~~'''~~Example~~'''~~ A domains with the full name <vp>\xxx\yyy\zzz\ccc::ddd</vp> can be as referenced <vp>zzz\ccc::ddd</vp> inside <vp>aaa</vp> because <vp>xxx\yyy</vp> is open.		{{Example\| A domains with the full name <vp>\xxx\yyy\zzz\ccc::ddd</vp> can be as referenced <vp>zzz\ccc::ddd</vp> inside <vp>aaa</vp> because <vp>xxx\yyy</vp> is open.
			}}

	Notice that the short name does not start with a backslash; A name starting with a backslash is always a full name.		Notice that the short name does not start with a backslash; A name starting with a backslash is always a full name.

	The namespace that a certain scope (i.e. interface/class/implementation) belongs to is (implicitly) open inside that scope.		The namespace that a certain scope (i.e. interface/class/implementation) belongs to is (implicitly) open inside that scope.

Alexander Doronin at 10:01, 18 October 2008

2008-10-18T10:01:06Z

← Older revision		Revision as of 12:01, 18 October 2008
Line 18:		Line 18:
	Namespace entrances divide source files into '''''namespace regions'''''.		Namespace entrances divide source files into '''''namespace regions'''''.

	A namespace entrance marks the beginning of a namespace region, which ~~ends~~ ends at the next namespace entrance or the end of the file.		A namespace entrance marks the beginning of a namespace region, which ends at the next namespace entrance or the end of the file.

	Every file starts in the '''''root namespace'''''.		Every file starts in the '''''root namespace'''''.

Thomas Linder Puls: update

2008-10-16T19:10:52Z

update

← Older revision		Revision as of 21:10, 16 October 2008
Line 53:		Line 53:
	The leading backslash indicates that we start from the root namespace.		The leading backslash indicates that we start from the root namespace.

	A class/interface can always be ~~uniqly~~ referenced using its full name.		A class/interface can always be uniquely referenced using its full name.

	The full names are not always convenient and therefore it is possible to use shorter names ~~in certain situations~~.		==== Open namespaces ====

			The full names are not always convenient and therefore it is possible to use shorter names by opening namespaces.

			<vipbnf><ScopeQualification>: one of
			<OpenQualification>
			...

			<OpenQualification>: one of
			open <NamespaceIdentifier> \
			...</vipbnf>

	~~==== Open namespaces ====~~		Opening a namespace is distinguished from opening a class/interface by a trailing backslash.

	~~First of all it is possible to <vp>open</vp> namespaces inside a scope:~~		'''Example'''

	<vip>class aaa		<vip>class aaa
Line 66:		Line 76:
	end class aaa</vip>		end class aaa</vip>

	~~Opening a~~ namespace is ~~distinguished from opening a class~~/~~interface by the trailing backslash~~.		The namespace <vp>xxx\yyy</vp> is opened inside <vp>aaa</vp>.

	~~The~~ namespace ~~that a certain scope (i.e. interface/class/implementation) belongs to~~ is ~~(implicitly)~~ open ~~inside~~ that ~~scope~~.		When a namespace is open that part of a full name can be left out.

	~~==== Namespace qualification ====~~		'''Example''' A domains with the full name <vp>\xxx\yyy\zzz\ccc::ddd</vp> can be as referenced <vp>zzz\ccc::ddd</vp> inside <vp>aaa</vp> because <vp>xxx\yyy</vp> is open.

	~~Since several namespaces be open simultaneously it is possible~~ that ~~names may clash. Using~~ the ~~full~~ name it is always ~~possible to resolve any ambiguity~~.		Notice that the short name does not start with a backslash; A name starting with a backslash is always a full name.

	~~But it is also possible to use '''''suffix qualification'''''. With suffix qualification you write~~ a ~~suffix of the namespace~~. ~~A suffix goes from right after a backslash to the end of the namespace identifier~~.		The namespace that a certain scope (i.e. interface/class/implementation) belongs to is (implicitly) open inside that scope.

	~~'''Example''' The suffixes of <vp>\xxx\yyy\zzz<~~/~~vp> are:~~

	~~<vip>xxx\yyy\zzz~~
	~~yyy\zzz~~
	~~zzz<~~/~~vip>~~

	~~So if <vp>aaa</vp>~~ is ~~a class in <vp>\xxx\yyy\zzz</vp>, these are the possible suffix qualifications:~~

	~~<vip>xxx\yyy\zzz::aaa~~
	~~yyy\zzz::aaa~~
	~~zzz::aaa</vip>~~

Thomas Linder Puls: header levels

2008-10-16T14:03:19Z

header levels

← Older revision		Revision as of 16:03, 16 October 2008
Line 57:		Line 57:
	The full names are not always convenient and therefore it is possible to use shorter names in certain situations.		The full names are not always convenient and therefore it is possible to use shorter names in certain situations.

	=== Open namespaces ===		==== Open namespaces ====

	First of all it is possible to <vp>open</vp> namespaces inside a scope:		First of all it is possible to <vp>open</vp> namespaces inside a scope:
Line 70:		Line 70:
	The namespace that a certain scope (i.e. interface/class/implementation) belongs to is (implicitly) open inside that scope.		The namespace that a certain scope (i.e. interface/class/implementation) belongs to is (implicitly) open inside that scope.

	=== Namespace qualification ===		==== Namespace qualification ====

	Since several namespaces be open simultaneously it is possible that names may clash. Using the full name it is always possible to resolve any ambiguity.		Since several namespaces be open simultaneously it is possible that names may clash. Using the full name it is always possible to resolve any ambiguity.

Thomas Linder Puls: /* Namespace qualification */ wiki markup bug

2008-10-16T14:02:19Z

Namespace qualification: wiki markup bug

← Older revision		Revision as of 16:02, 16 October 2008
Line 80:		Line 80:
	<vip>xxx\yyy\zzz		<vip>xxx\yyy\zzz
	yyy\zzz		yyy\zzz
	zzz<vip>		zzz</vip>

	So if <vp>aaa</vp> is a class in <vp>\xxx\yyy\zzz</vp>, these are the possible suffix qualifications:		So if <vp>aaa</vp> is a class in <vp>\xxx\yyy\zzz</vp>, these are the possible suffix qualifications:
Line 86:		Line 86:
	<vip>xxx\yyy\zzz::aaa		<vip>xxx\yyy\zzz::aaa
	yyy\zzz::aaa		yyy\zzz::aaa
	zzz::aaa<vip>		zzz::aaa</vip>

Thomas Linder Puls: /* Namespace Entrances and Regions */ Referencing

2008-10-16T13:59:41Z

Namespace Entrances and Regions: Referencing

← Older revision		Revision as of 15:59, 16 October 2008
Line 46:		Line 46:

	Subsequently, the class <vp>aaa</vp> belongs to the root namespace, the class <vp>bbb</vp> belongs to the namespace <vp>xxx</vp> and finally the class <vp>ccc</vp> belongs to the namespace <vp>xxx\yyy</vp>.		Subsequently, the class <vp>aaa</vp> belongs to the root namespace, the class <vp>bbb</vp> belongs to the namespace <vp>xxx</vp> and finally the class <vp>ccc</vp> belongs to the namespace <vp>xxx\yyy</vp>.

			=== Referencing names in namespaces ===

			If <vp>ccc</vp> is a class in the namespace <vp>xxx\yyy</vp>, then the '''''full name''''' of <vp>ccc</vp> is <vp>\xxx\yyy\ccc</vp>.

			The leading backslash indicates that we start from the root namespace.

			A class/interface can always be uniqly referenced using its full name.

			The full names are not always convenient and therefore it is possible to use shorter names in certain situations.

			=== Open namespaces ===

			First of all it is possible to <vp>open</vp> namespaces inside a scope:

			<vip>class aaa
			open xxx\yyy\
			...
			end class aaa</vip>

			Opening a namespace is distinguished from opening a class/interface by the trailing backslash.

			The namespace that a certain scope (i.e. interface/class/implementation) belongs to is (implicitly) open inside that scope.

			=== Namespace qualification ===

			Since several namespaces be open simultaneously it is possible that names may clash. Using the full name it is always possible to resolve any ambiguity.

			But it is also possible to use '''''suffix qualification'''''. With suffix qualification you write a suffix of the namespace. A suffix goes from right after a backslash to the end of the namespace identifier.

			'''Example''' The suffixes of <vp>\xxx\yyy\zzz</vp> are:

			<vip>xxx\yyy\zzz
			yyy\zzz
			zzz<vip>

			So if <vp>aaa</vp> is a class in <vp>\xxx\yyy\zzz</vp>, these are the possible suffix qualifications:

			<vip>xxx\yyy\zzz::aaa
			yyy\zzz::aaa
			zzz::aaa<vip>

Thomas Linder Puls: word choice

2008-10-16T12:41:40Z

word choice

← Older revision		Revision as of 14:41, 16 October 2008
Line 43:		Line 43:
	end class ccc</vip>		end class ccc</vip>

	~~The~~ file is divided in three regions (assuming that it is a complete file). The first region is in the root namespace (\), the second region belongs to the <vp>xxx</vp> namespace and the third region belongs to the <vp>xxx\yyy</vp> namespace.		This file is divided in three regions (assuming that it is a complete file). The first region is in the root namespace (\), the second region belongs to the <vp>xxx</vp> namespace and the third region belongs to the <vp>xxx\yyy</vp> namespace.

	Subsequently, the class <vp>aaa</vp> belongs to the root namespace, the class <vp>bbb</vp> belongs to the namespace <vp>xxx</vp> and finally the class <vp>ccc</vp> belongs to the namespace <vp>xxx\yyy</vp>.		Subsequently, the class <vp>aaa</vp> belongs to the root namespace, the class <vp>bbb</vp> belongs to the namespace <vp>xxx</vp> and finally the class <vp>ccc</vp> belongs to the namespace <vp>xxx\yyy</vp>.

Thomas Linder Puls: regions

2008-10-16T12:39:44Z

regions

@@ Line 1: / Line 1: @@
 {{languageReferenceNavbar|Namespaces}}
-<vipbnf><NamespaceDeclaration> :
+Namespaces can be used to avoid name clashes, without having to use long strange names. The names in two different namespaces will never clash, but it may be necessary to qualify references with the namespace (or part of it) to resolve ambiguities.
     namespace <NamespaceIdentifier></vipbnf>
 <vipbnf><NamespaceIdentifier>: one of
-    <backslashSeparatedIdentifier>
+    <LowercaseIdentifier>
-    \ <backslashSeparatedIdentifier></vipbnf>
+    <LowercaseIdentifier> \ <NamespaceIdentifier></vipbnf>
-<vipbnf><backslashSeparatedIdentifier>: one of
+Subsequently, the class <vp>aaa</vp> belongs to the root namespace, the class <vp>bbb</vp> belongs to the namespace <vp>xxx</vp> and finally the class <vp>ccc</vp> belongs to the namespace <vp>xxx\yyy</vp>.