Thank you for downloading the Java Toolkit Collection API.
The Java Toolkit Collection API consists of several Sub-APIs.
Each Sub-API is implemented by a Java class.
The JTC-API is a non-object-oriented class library.
Most methods of the JTC-API are static,
therefore these methods can be called anywhere in your source code.
Critics can ask why object-oriented programming was not applied in this class library.
One reason is that, source code integration becomes more understandable.
Another reason is that, introducing new classes is difficult in a team.
If we would have extended for example the class String to create a new class String2,
then all project-members would have to train themselves into this new class.
An example of a function call would be:
boolean b = softhema.system.toolkits.ToolkitString.isLike( "Example", "E*e" );
For a programmer it is evident that the method isLike is a function extension
and does not belong to the core API of Sun.
If one would have extended the class String instead,
then the code would look as follows:
String2 s = new String2("Example");
boolean b = s.like("E*e");
First of all, members of your team would be forced to accept the class String2.
Secondly one could mistaken class String for class String2, by overlooking the "2" placed behind.
We decided therefore to structure the JTC-API as a function library.
|
