![]() ![]() Implementations, i.e., Classes − These are the concrete implementations of the collection interfaces. In object-oriented languages, interfaces generally form a hierarchy. Interfaces allow collections to be manipulated independently of the details of their representation. ![]() Interfaces − These are abstract data types that represent collections. All collections frameworks contain the following − Several standard implementations such as LinkedList, HashSet, and TreeSet, of these interfaces are provided that you may use as-is and you may also implement your own collection, if you choose.Ī collections framework is a unified architecture for representing and manipulating collections. Towards this end, the entire collections framework is designed around a set of standard interfaces. The framework had to extend and/or adapt a collection easily. The framework had to allow different types of collections to work in a similar manner and with a high degree of interoperability. The implementations for the fundamental collections (dynamic arrays, linked lists, trees, and hashtables) were to be highly efficient. The framework had to be high-performance. The collections framework was designed to meet several goals, such as − Thus, the way that you used Vector was different from the way that you used Properties. Although these classes were quite useful, they lacked a central, unifying theme. ![]() Prior to Java 2, Java provided ad hoc classes such as Dictionary, Vector, Stack, and Properties to store and manipulate groups of objects. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |