building own library with include-files?

[mister_e]

C'est a peu pres ca que je voulais dire Darrel mais en Anglais!

I should develop much more on every arguments next time... sorry

And, always using the same method / coding style, is a sure fire way to make sure you never find it.

I wasn't unclear enough once again... I meant in the way you structure your program, not the way you code it. BTW how many different method can we use to blink a LED??? XOR the PIN, USE HIGH/LOW, TOGGLE, with PAUSE, Use internal Timer to produce delay and so on wich is better?? the tight one, the readable one, the assembler one....... the one you're confortable with i guess. even if i'll more than often prefer the tight one. Probably the same thing for most who design stuff to be done in multiple copy.

Filling a PIC memory is easy. Everybody here can fill a 8K with a few different task/feature. Filling the same PIC with a maximum of task/option/feature by using all or a maximum of internal ressource and make things impossible to add extra feature is an art. Is this makes you a better programmer?? If the BOM is lower and the benefit are higher, your boss will probably agree.

Try new approaches to problems that you've already solved before. Learn what advantages one method has over the other, so that you can avoid the disadvantages the next time

I agree. Some will say i'm a pure dumb and have no life but... one thing i do to relax myself, is to open an old code i did and try to shrink it as much as i can. OR trying different method as you said. Those i did on a rush request and those posted by user on different forum are my favourite. Yeah i can change the Coding style, the way to do one/multiple tasks but not the 'program template' or the order i place/declare things in a program.

Anyway, How to stucture, how to program and ALL 'How to' will be always an endless story.

Mmm... It's amazing to have as this few reply here...