RE: [Avr-libc-corelib] proposed corelib style guide

[Jan Waclawek]

>> I would anticipate that users will copy the library files to their
>> projects, potentially modifying them, rather than use a pre-built
>> library or such.
>> So the usage guideline should include a method how to add all that's
>> necessary into a makefile, preferrably "compatible" with mfile's
>> "standard" output (or shall we attempt to expand mfile's capabilities
>> accordingly?)
>> 
>
>As I understand it, the library will be a pre-compiled lib file, with the
>MCU name in the makefile linking to the matching version for that processor.


Making things bulletproof usually makes them way too rigid and
heavyweight. And then they are far from being perfect.

Although this would need to be confirmed by a poll or similar, I assume
that most users of the Procyon library make modifications to it at some
point anyway.


>Maintaining a source version would be nigh on impossible. Imagine: "I
>increased the buffer limit and changed the speed setting and now my app
>resets about every 5 minutes. Help!".


Contrary: this might give good pointers to further development of the
library.


JW