On Tue, 27 May 2008, Michael N. Moran wrote: > Analyzing the many AVR peripheral variations and > developing a properly factored design is a real > time consumer.
I intend to analyze precisely 4 sets. > If refactoring is applied as new devices are > implemented, a peripheral framework can evolve, > rather than being designed all at once. The code This is more or less what I had in mind. It was inspired in part by the tininess of the differences in the timers and in part by the even tinier diffeerences in their class names. > will be volatile in the early stages, and eventually > converge. The volatility can be reduced by doing > more up-front analysis and design... a > basic engineering trade-off. > > IMHO, its the active itch scratchers that decide. -- Michael [EMAIL PROTECTED] "Those parts of the system that you can hit with a hammer (not advised) are called Hardware; those program instructions that you can only curse at are called Software." _______________________________________________ Simulavr-devel mailing list Simulavr-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/simulavr-devel