Differences between version 4 and revision by previous author of NamespaceCollision.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 4 | Last edited on Thursday, September 11, 2003 12:56:16 pm | by StuartYeates | Revert |
| Older page: | version 3 | Last edited on Friday, July 26, 2002 9:41:30 pm | by CraigBox | Revert |
@@ -6,4 +6,6 @@
; Namespace : A namespace is much what it sounds like - a finite space that names can be defined and identified in. For example, if you're writing a program and you wanted to define a class called Object, you'd be out of luck as the class Object already exists. If you were able to define a second class called Object, how would the computer know the difference between the two?
; Namespace collision : When two companies/groups/people try to name thier classes with the same name, or define methods off of a class with the same name. To help avoid namespace collision not only within your own projects, but from other companies like third party vendors, it's a common practice to prefix your classes with some acronym, for example, if you work for MegaCorp you might prefix all your classes with 'Mc'
+
+See also: [NameSpace].
