Refactor Lattice Element

[GoogleCodeExporter]

We are going to get rid of LatticeElement. This has several sub-tasks:

1. Creation of LatticeOps<T>, which defines atLeastAsPrecise and join

2. Parametrize the transfer functions by the generic lattice data, T

3. Removing Lattice, putting functionality into transfer functions. 

Please make sure there is a release with the old interfaces.

Original issue reported on code.google.com by ciera.christopher on 17 Mar 2009 at 9:05

[GoogleCodeExporter]

New interface introduced, but existing lattices mostly use old functionality 
(using
new bridge class as explained below).  Recommend refactoring existing lattice 
element
implementations and moving away from using TupleLatticeElement in particular.

* Introduced ILatticeOperations; moved existing LatticeElement interface into 
new
"simple" package with r157.  Required changing transfer function interface and 
other
changes. 

* Removed Lattice class and some other deprecated classes.  

* Introduced "bridge" class LatticeElementOps to make using existing 
LatticeElement
implementations easier.

* Retrofitted existing analyses.

Original comment by kevin.bi...@gmail.com on 19 Mar 2009 at 10:27

• Changed state: Started
• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

I am finalizing the refactor as part of the crystal enhancements for education.

Original comment by ciera.christopher on 22 May 2009 at 8:39

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

I put the bridge classes into a bridge package so plural can continue using 
them.

Original comment by ciera.christopher on 27 May 2009 at 3:07

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Original comment by ciera.christopher on 27 May 2009 at 3:08

• Changed state: Fixed
• Added labels: ****
• Removed labels: ****