[DynInst_API:] upcoming releases and potential API changes

[Bill Williams <bill@xxxxxxxxxxx>]

Two things here:

1) Dyninst 8.2.1 is coming soon, pending evaluation of fixes for a 
couple more bugs that have been reported in 8.2.0.
2) We're looking at potential API-breaking changes that have been 
floating around our TODO list, as we've got at least one good reason to 
break the API (loops) that's already been discussed. Other things I can 
think of:
* The instructionAPI bind/eval mechanism has basically been superseded 
by the visitor mechanism, which is more space-efficient and cannot alter 
the actual contents of an instruction unintentionally. I'd like to 
remove that interface, leaving just type information for each node of 
the operand ASTs. Objections?
* Line information is likely to need a redesign for space efficiency, as 
will some parsing data structures. In both cases we'll be preserving 
typedefs where possible but changing underlying types--and we may not be 
preserving full interface compatibility if anyone was relying on the 
behavior of a particular container. Again, objections?
If anyone has nominations for other interfaces that should be 
changed/deprecated/deleted in our next major release, let us know.

--bw

Bill Williams
Paradyn Project
bill@xxxxxxxxxxx