[deepamehta-devel] [Bug #14005] Old collection classes are used

[admin at berlios.de]

Bug #14005, was updated on 2008-Jun-10 14:26
Here is a current snapshot of the bug.

Project: DeepaMehta
Category: None
Status: Open
Resolution: None
Bug Group: None
Priority: 1
Submitted by: jri
Assigned to : url
Summary: Old collection classes are used

Details: Note: the following is not actually a bug report but the description of a sourcecode maintenance task.

Since the DeepaMehta project started before the Java Collections Framework was introduced in Java 1.2 the DeepaMehta sourcecode makes heavy use of the now obsolete collection classes "Vector", "Hashtable", and "Enumeration". This is not a problem at all, but new developers will probably use the current incarnations, such as "ArrayList", "HashMap", and "Iterator". In order to avoid confusion and for the sake of "beauty" it is preferred not mix the old and the new style.

So: the complete DeepaMehta sourcecode should incrementally transformed to the canonical style of the Java Collections Framework. That is to make the following replacements of classes:

Vector -> ArrayList
Hashtable -> HashMap
Enumeration -> Iterator

This task should be seen as formal and non-creative work. In particular, no checks/assertions and no logic should be added. Just replacements, no additions. There are hundreds, if not thousands, spots to transform. Trying to combine this uniform task with the ambition of quality improvements woud probably render this an endless endeavour. The current code is running well and is well understood. Logical changes/additions would not necessarily improve the quality of code but possibly reduce the level of understanding among the present developers.

So: this task is suited to novice developers or to people who want to return to Java-practice after a phase of non-programming.

Important: all DeepaMehta sourcecode must compile and run in Java 1.4. Therefore we can't use the newer Java concept of Generics and the new loop syntaxes as introduced in Java 1.5.


For detailed info, follow this link:
http://developer.berlios.de/bugs/?func=detailbug&bug_id=14005&group_id=5174