It would probably be possible to implement the ELIST2 classes as derived classes from ELIST. I haven't done this because:
- I think it would be harder to understand the code (Though the problem with not inheriting is that changes to ELIST must be reflected in ELIST2 and vice versa)
- Most of the code is inline so:
- The duplication in source does not affect the run time code size - the code is copied inline anyway!
- The compiler should have a bit less work to do!
Generated on Wed Feb 28 19:49:30 2007 for Tesseract by