PerformanceOrientedCoreUtils Code
Brought to you by:
patton99
File | Date | Author | Commit |
---|---|---|---|
build | 2008-01-06 | patton99 | [r1] Initial import |
doc | 2008-01-06 | patton99 | [r1] Initial import |
lib | 2008-01-06 | patton99 | [r1] Initial import |
src | 2009-01-14 | patton99 | [r63] updates to TreeMap |
BUILD.txt | 2008-08-01 | patton99 | [r37] added .txt extension to text files in pocu root... |
COPYING.LESSER.txt | 2008-08-01 | patton99 | [r37] added .txt extension to text files in pocu root... |
COPYING.txt | 2008-08-01 | patton99 | [r37] added .txt extension to text files in pocu root... |
Makefile | 2008-12-15 | patton99 | [r53] added Context.setToState(state), renamed Contex... |
README.txt | 2008-08-01 | patton99 | [r37] added .txt extension to text files in pocu root... |
PerformanceOrientedCoreUtils Copyright 2007 John Patton This package is a set of data structures and other core utilities designed to replace those provided by Java, although they are not meant to be drop-in replacements. Instead they are a complete re-think focused on performance and usability in a production environment. They are designed to be reliable and efficient, as well as easy to use. Given their status as fundamental utility classes their names are abbreviated in a cohesive way in order to save on typing. Alot of time and thought went into each class in order to maximize performance and correctness. In short, they are meant to be professional quality development tools. Long-term usability is considered important, and so it is a policy that the internal mechanics of existing structures will not be changed in ways that affect performance characteristics (so much as it is possible). For example, the Stack uses a linked list right now. It will never be changed into an array based structure; instead a new class will be created. Same with methods. Once committed into public release, methods will not be removed or changed in signicant ways (except to fix bugs); alternate functionality will instead get added in a new methods. But new methods will not be allowed in if they require additional overhead to existing methods and processes or otherwise degrade the primary functionality of the class. As a deeply connected, core part of a system, the data structures must forever remain stable. It is critical for the classes in this project to be absolutely bug free. To be usable in any sort of major application they must be completely trustworthy. I have done my best to test them thoughly, but if you discover a bug please let me know at <patton99@users.sourceforge.net>. Describe it precisely, and provide a fix if you can! Any help received in testing will be of benefit to us all. --- If you would like to contribute or have good ideas that you would like to share, you can reach me at <patton99@users.sourceforge.net>. Be sure to look at the TODO files in each project directory if you want to help.