So we look at how we can access packages and also how we can create packages. 2
No let's see how we should name packages. 3
That is we will look at standard conventions for naming packages through a simple example let's just 4
look at a problem that the man conter due to bad off naming packages. 5
Let's have you have an idea who is a student at Stanford University let's assume Anita has developed 6
a math library which is available for download for public use. 7
One of the packages in this library is named as Mad Dog geometry non-IT Ajume there's a guy called John 8
who works for Oracle. 9
Let's Ajan also don't have the publicly available math library which also includes a package called 10
Mad Dog geometry not assume that book on it does matter door geometry and. 11
My documentary packages look very similar as most of methods have identical signatures although their 12
implementations are quite different. 13
Not have the company semi-big square on one of their projects is heavily in demand and they're already 14
using and it does a bit not it's a semantic Square has a new and don't call bought and bought comes 15
across. 16
John celebrity and wants to use its modern geometry package. 17
So he tries to use it and to his surprise it doesn't work as expected. 18
After some investigation he finds that at runtime JVM is actually using and it does matter geometry 19
package insert off John's package. 20
Naturally this irritates Bob as you can see from his expression So basically the two packages with the 21
same name JVM is always picking on its package. 22
So there is a package named conflict here and this is because both are not on John. 23
We're not following proper Bakhash naming conventions. 24
So all packages are supposed to work class name conflicts they missed and not be helpful. 25
If the developers do not follow proper naming conventions do what package name conflicts recommend the 26
convention is to use the organizations to reverse Internet domain name one example our little engine 27
could have named their packages are shown here on it from Stanford University whose domain is Stanford 28
not to you. 29
So she could have started her package name with the reverse of the domain name which would be edu Daut 30
Stanford Similarly John could have started his package name with com dot article. 31
This would have and or bought to use Johnson Library without any issues there are so few other naming 32
conventions item 56 ineffective is all about naming conventions and it actually starts with naming conventions 33
for packages. 34
Here we discuss only the ones pertaining to packages. 35
All of the recommendations will be discussed later. 36
Towards the end of language basic series Hussman says that components in a package should consist off 37
what gets alphabets on really digits component should also be shot generally eight or fewer characters 38
meaningful abbreviations like you do for utilities are encouraged like in the case of Gelada acronyms 39
or find do for example there is a package called AWB which is related to creating user interfaces hit 40
N.W.T. is an acronym for abstract window toolkit Jindalee component should consist of only a single 41
word Hundley you should know what stock you are packaged in the Java Oddjob X used with a standard July 42
. 43
The majority of packages in July be stocked with giallo Jorak seems to exist only for historical reasons 44
. 45
One son wanted to use it for only extensions that is called classes would reside within Java while extensions 46
would be in jail X Java Swing API falls under Jagex So these are some naming conventions specific to 47
packages. 48
And you should really buy them. 49
So that's about it. 50
And that's the I know forward discussion on packages. 51
Thank you