Presentation is loading. Please wait.

Presentation is loading. Please wait.

Data structures and algorithms in the collection framework 1 Part 2.

Similar presentations


Presentation on theme: "Data structures and algorithms in the collection framework 1 Part 2."— Presentation transcript:

1 Data structures and algorithms in the collection framework 1 Part 2

2 Data structures and algorithms in the collection framework 2 Interfaces Collection –Methods common to all collections (except map) List –An ordered collection. Set –No duplicate elements. –equals(Object obj) method on the elements is important. Queue –Normally implemented as FIFO (first-in-first-out) –New in Java 5.0 SortedSet –Set that guarantees that elements are traversed in order Map –Contains pairs (key, value) –Values are retrieved by the key: value = map.get(key) SortedMap –Map that guarantees that elements are sorted according to the key.

3 Data structures and algorithms in the collection framework 3 Implementations overview General purpose implementations Interfaces Hash table Resizable array Balanced tree Linked List SetHashSetTreeSet ListArrayListLinkedList MapHashMapTreeMap

4 Data structures and algorithms in the collection framework 4 Wrapper implementations The “wrapper” idea –Goals: Extend the functionality of an object transparent to its clients (i.e. the users of the class) Known examples are diff. streams Two kinds of wrappers in the collection framework –Synchronized wrappers –Unmodifiable wrappers

5 Data structures and algorithms in the collection framework 5 Synchronized wrappers Purpose –Collection implementations are generally unsynchronized Methods are not synchronized Exceptions to the “rule”: Vector, HashTable (old implementations) –Synchronized collections can be made using methods in the class Collections. Static methods in class Collections –Collection synchronizedCollection( Collection c ) –List synchronizedList( List l ) –Set synchronizedSet( Set s ) –Map synchronizedMap( Map m )

6 Data structures and algorithms in the collection framework 6 Unmodifiable wrappers Purpose –Collections are generally modifiable They have methods like add, remove, etc. –Unmodifiable collections can be made using methods in the class Collections If you attempt to call modifying methods like add, remove, etc. you will get an UnsupportedOperationException. –Not very good object-oriented design, but it works. Static methods in class Collections –unmodifiableCollection( Collection c ) –unmodifiableList( List l ) –unmodifiableSet( Set s ) –unmodifiableMap( Map m )

7 Data structures and algorithms in the collection framework 7 Decorator pattern Also know as “wrapper pattern”. Synchronized wrapper and unmodifiable wrapper are applications of the decorator pattern. Idea –Extend the functionality of an object transparent to its clients (i.e. the users of the class) How –A class extends another class and at the same time aggregates an object of the super class. –Methods in the subclass does something special and call the super class’ method for the basic work. Alternative to (lots of) inheritance Used intensively in java.io –BufferedReader wraps any Reader Providing buffering, for speed.

8 Data structures and algorithms in the collection framework 8 Layered implementation Interface –a specification Abstract class –a partly implementation of a specification –Used by one or more [concrete] classes [Concrete] class –Implementation of a specification Example –List: Interface –AbstractList: Partial implementation –ArrayList and LinkedList: [Concrete] implementations

9 Data structures and algorithms in the collection framework 9 Custom implementations Reasons for writing a custom implementation –Persistency You want the collection to reside on the hard disk (file or database), not just in main memory. –High performance, special purpose You want a fast implementation for some special purpose. Use an abstract class (partial implementation) if possible –It will do most of the work.

10 Data structures and algorithms in the collection framework 10 Algorithms Class Collections and class Arrays –Not to be confused with the interface Collection Some static methods –Sorting lists –Searching ordered lists –Finding extreme values (max, min)

11 Data structures and algorithms in the collection framework 11 Sorting lists Works with lists –Not general collections, since they have no notion of a sequence. Algorithm: Merge sort –Fast: n*log(n) guaranteed, even faster on nearly sorted lists. –Stable: Doesn’t reorder equal elements. –Idea: Divide and conquer + recursion Divide the list in 2 sub-lists and sort the sub-lists. Conquer: Merge the small lists. http://www.codecodex.com/wiki/index.php?title=Merge_sort Methods –Collections.sort( List l ) –Collections.sort( List l, Comparator c ) If you want to use your own comparator, not the natural order.

12 Data structures and algorithms in the collection framework 12 Searching ordered lists Works with ordered lists –Not general lists If the list is not ordered, use Collections.sort( List l ) before searching –Not general collections Algorithm: Binary search –Speed O( log n ) for random access list implementations (like ArrayList) O( n ) for iterator-based list implementations (like LinkedList) –Idea: Divide-and-conquer + recursion Find the middle element. If middle element < searchingFor –Search in the left hand part of the list Else –Search the right hand part of the list Methods –Collections.binarySearch( List l, Object searchingFor ) –Collections.binarySearch( List l, Object searchingFor, Comparator c ) If the list is not ordered by the natural order, but by the specified comparator.

13 Data structures and algorithms in the collection framework 13 Finding extreme values Finds min, max in any collection –Algorithm is iterator-based. –If the collection is known to be ordered don’t used min, max. Simply call get(0) or get( size() ) Methods in Collections –Object min( Collection c ) –Object max( Collection c ) –Object min( Collection c, Comparator c ) –Object max( Collection c, Comparator c ) If you prefer your own comparator to the natural order.

14 Data structures and algorithms in the collection framework 14 Arrays Algorithms similar to Collections Working on arrays of different types –int, double, etc. and Object Convenience methods –List view of arrays List list = Arrays.asList( someArray ) Useful for printing an array –System.out.println( list ) –System.out.println( Arrays.asList(someArray) ) –Java 5.0 System.out.println( Arrays.toString(someArray) )

15 Data structures and algorithms in the collection framework 15 The term “framework” The term “framework” denotes a set of classes that can be extended … Examples –Collections framework You can extend the framework creating your own implementations –Swing You can extends the framework extending JPanel and many other classes. –java.io Some frameworks can be used as is – others need custom extensions before they are useful.

16 Data structures and algorithms in the collection framework 16 Hashing Binary search is O( log n ) We want something better: O(1) Idea: –Compute a number (called “hash value”) from the data we are searching for. –Use the hash value as an index in an array (called “hash table”) –Every element in the array holds a “bucket” of elements. –If every bucket holds few elements (preferably 1) then hashing is O(1)

17 Data structures and algorithms in the collection framework 17 Hash function A good hash function should distribute elements evenly in the hash table –The worst hash function always returns 0 Example –Hash table with 10 slots –hash( int i ) { return i % 10; } % is the remainder operator. –More generally Hash table with N slots hash( T t ) { return operation( t ) % N; } –The operation should be fast and distribute elements well. Java, class Object –int hashCode() is a hash function Your classes should override hashCode() hashCode() and equals() –a.equals(b) is true ⇒ a.hashCode() == b.hashCode() –a.hashCode() == b.hashCode() ⇒ a.equals(b) is truenot necessarily! –a.hashCode() != b.hashCode() ⇒ a.equals(b) is false

18 Data structures and algorithms in the collection framework 18 Hash table A hash table is basically an array. What if 2 elements computes the same hash value (i.e. same array index)? –Two solutions Linear probing: 1 element in every array cell –Try the next empty slot in the hash table –Mark slots as “here was once an element” Chaining: A list of elements in every array cell –Add the element to the list In any case searching can degenerate if the hash function does not distribute elements evenly. Problem –If a hash table is almost full searching degenerates Solution –Rehashing: Create a larger hash table + update hash function + move elements to new hash table.

19 Data structures and algorithms in the collection framework 19 Binary search tree Basic tree terms –Node, descendant, root, leaf –A tree has 1 root Binary tree –A node has at most 2 (bi-) descendants. Search tree –Nodes are ordered. Small values to the left and large values to the right. –Makes searching fast.

20 Data structures and algorithms in the collection framework 20 Balanced search trees A binary search tree might degenerate into a list. –Searching is no longer fast We want the search tree to be balanced. –Without having to completely reorganize the tree at every insert / delete.


Download ppt "Data structures and algorithms in the collection framework 1 Part 2."

Similar presentations


Ads by Google