Fully qualified name
 |
It has been suggested that Fully qualified file name be merged into this article or section. (Discuss) Proposed since October 2011. |
|
|
It has been suggested that Fully qualified path name be merged into this article or section. (Discuss) Proposed since November 2011. |
 |
This article may need to be rewritten entirely to comply with Wikipedia's quality standards. You can help. The discussion page may contain suggestions. (October 2011) |
 |
This article may contain excessive, poor or irrelevant examples. You can improve the article by adding more descriptive text and removing less pertinent examples. See Wikipedia's guide to writing better articles for further suggestions. (October 2011) |
In computer programming, a fully qualified name is an unambiguous name that specifies which object, function, or variable a call refers to without regard to the context of the call.[citation needed] In a hierarchical structure, a name is fully qualified when it "is complete in the sense that it includes (a) all names in the hierarchic sequence above the given element and (b) the name of the given element itself."[1] Thus fully qualified names explicitly refer to namespaces that would otherwise be implicit because of the scope of the call.[2] While always done to eliminate ambiguity, this can mean different things dependent on context.
Commonly encountered applications of the notion have been given their own names, such as the fully qualified domain name and the fully qualified file name.
[edit] Examples
To distinguish a fully qualified name from a regular name, C++, Tcl, Perl and Ruby use two colons (::), and Java uses dots (.), as does Visual Basic .NET.[3] and C#.[4] In Java, ActionScript,[5] and other object-oriented languages the use of the dot is known as "dot syntax".[6] Other examples include:
- As an example of a relational database, in Microsoft SQL Server the fully qualified name of an object is the one that specifies all four parts:
server_name.[database_name].[schema_name].object_name.[7]
- In Perl, a fully qualified scalar (
$scalar) that is in the packagepackage2would be referred to as$package2::scalar[8]
- In Unix pathnames, instead of referring to
./foo/bar/baz.shin/home/user/quz, which uses a relative pathname, the fully qualified name would be/home/user/quz/foo/bar/baz.shThis is an example of a fully qualified file name.[9]
- In the sense of domain names, a fully qualified domain name is explicitly suffixed with a dot, to eliminate the step of resolving, and to ensure that no additional suffix is added:
wikipedia.com.for instance. This is an example of a fully qualified domain name.[10]
[edit] References
- ^ Weik, Martin H. (2000). Computer Science and Communications Dictionary. Volume 1. Springer. p. 662. ISBN 978 0792384250. http://books.google.com/books?id=gbP1bLDPKlYC&pg=PA662.
- ^ Hejlsberg, Anders; Torgersen, Mads; Wiltamuth, Scott (29 October 2010). The C# Programming Language (Covering C# 4.0). Addison-Wesley Professional. p. 190. ISBN 978-0-13-248172-4. http://books.google.com/books?id=s-IH_x6ytuQC&pg=PT190. Retrieved 28 October 2011.
- ^ Vick, Paul (2004). The Visual Basic .NET programming language. Addison-Wesley Professional. p. 160. ISBN 978 0321169518. http://www.google.co.uk/books?id=ejzRTF2TL6UC.
- ^ Mayo, Joe. ": C# Tutorial Lesson 06 - Namespaces". C# Station. http://www.csharp-station.com/Tutorials/Lesson06.aspx. Retrieved 2011-10-27.
- ^ "ActionScript 3 fundamentals: Packages". Adobe Systems Incorporated. http://www.adobe.com/devnet/actionscript/learning/as3-fundamentals/packages.html. Retrieved 2011-10-27.
- ^ "Object Oriented Programming - JavaScript Programming Fundamentals - DHTML". Lanoie.com. http://www.lanoie.com/classes/DHTML/programming/lectures/lecture2.html. Retrieved 2011-10-27.
- ^ "Using Identifiers As Object Names". msdn.microsoft.com. http://msdn.microsoft.com/en-us/library/ms187879.aspx. Retrieved 2011-10-27.
- ^ "mod_perl: Perl Reference". perl.apache.org. http://perl.apache.org/docs/general/perl_reference/perl_reference.html. Retrieved 2011-10-23.
- ^ Kochan, Stephen G.; Wood, Patrick H. (2003). UNIX Shell programming. Sams Publishing. p. 11. ISBN 978-0-672-32490-1. http://books.google.com/books?id=hxEL__hcpSoC&pg=PA11. Retrieved 28 October 2011.
- ^ Lowe, Doug (8 February 2011). Networking For Dummies. For Dummies. p. 80. ISBN 978-1-118-05100-9. http://books.google.com/books?id=jc98S6PitdkC&pg=PT80. Retrieved 28 October 2011.
