Hi, Michael Hennebry: > The PINx toggle of PORTx bits is not a new feature. > simulavr must support this. > A RMW implementation of SBI also does not work on registers with interrupt > flags.
At least according to avrlibc doc, this is not recommended for interrupt flags: http://www.nongnu.org/avr-libc/user-manual/FAQ.html#faq_intbits http://www.atmel.com/webdoc/avrlibcreferencemanual/FAQ_1faq_intbits.html > That does not imply the goodness of a major data structure organization. > I note that an SBI instruction can only address registers on which it works. > Allowing extra functionality in other registers should not cause problems. > > Note that on some old AVRs, SBI *is* RMW and their datasheets reflect this. > > The confusing cyclic reference is called the curiously recurring template > pattern. > Not evil. > Pointers to void are not preferable. > As a rule, in C++, pointers to void are a bad idea. what about pointers to Hardware instead? This is the least common denomininator. This should also avoid the template altogether, shouldn't it? > I'm not clear on the template parameter type issue. > template <typename T> class { ... public: typedef T parametertype; ... } ; Cheers, panic _______________________________________________ Simulavr-devel mailing list Simulavr-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/simulavr-devel