Magnus Lundin wrote: > The tap state engine will not change any time soon. > > Hopefully the statenumbers will stay. > > But there will probably be work on shortest path tables, path transition > tables with fixed mumber of tap transition etc. For this type of work I > think an array is a better and less error prone representation than a > big set of nested switches. It is graphic :) and that is good. I can > also play with and debug array repsentations of state graphs in other > tools like Octave. This very good way to check the validity and catch > errors. Actually, now when I think about this, it should be possible to > generate the arrays with some Octave/Matlab code and calculate path lengths. > > So my wote goes for arrays. > > Regards > Magnus >
How should we count your vote, with or without array out of bounds checking? Dick _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
