RE: [avr-libc-dev] [RFC] New eeprom.h

[Michael Hennebry]

On Wed, 16 Jan 2008, Weddington, Eric wrote:

> - One big reason to move away from compiling code to macros, is that we
> do *not* have a true multi-lib (per device) environment with avr-libc.
> We need to be able to have different variants of code for different
> devices (not just per architecture). Right now, the only way for us to
> do this *is* with macros in a header file.

Additionally, someone who does want a function can write one rather easily.

-- 
Michael   address@hidden
"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."