> As for this specific case: we (well... ask you, Rob ;) > could add the > required code to the device file with conditional compile > dependent on > a a constant like SET_OSCCAL. So the device file is still > compliant to > the design rule unless you tell it otherwise.
Well, from a practical sight: What harm would be done if OSCCAL would be set unconditionally? It would require one word of code space that could be saved otherwise. If OSCCAL would be used in some other way, the user program would have to overwrite it anyway. Yes, it does not comply with the style. But I wouldn't mind in this case, as I can see no use for any program to rely on OSCCAL being set to its uncalibrated default value. Greets, Kiste -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
