Olin Lathrop wrote:
>> The problem with this approach, is that you have to manually port
>> whatever changes you make, back into the template.
>
> No I don't.  These changes are presumably one-off unique to that project.
> Unless I think they may be useful in other projects there would be no 
> point
> in backing them into the template.  Then there would need to be ways to
> select which features you want in the template.  Some amount of
> customization with assembly time conditionals may be worth it, but you 
> don't
> want something so dense it becomes hard to maintain and customize as 
> needed.

This is possible because your template is pretty much set in stone by now. 
New modules (at least in my experience) tend to go through lots of changes, 
before the dust finally settles.

If was working on the lower-end 8 bit PICs, your approach would make total 
sense. On the 24H, resources are cheap, and priorities are different.

Best regards,

Vitaliy 

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist