Joep Suijs wrote:
> A new thread for this issue that came up:

> Call at include-time ensures the init can not be forgotten, which is a
> good thing.
> Not calling it at include time seems to give more flexibility. But I
> can't think of a practical situation where one would need this kind of
> flexibility.

Well, being an old-age programmer ;-) I'm used to the fact that include 
header files in C-language do not execute code at program start. And I'm 
also used to call a function only at the moment I need it. Thus so far 
in my PIC programs I had no reason to do it differently....
When I saw the first time setup() being called by the library itself it 
was sort of a shock to me. But I realized quickly the advantage.

> Please let me know what you think.

My vote: let the library do the setup().

Regards, Rob.

-- 
Rob Hamerling, Vianen, NL (http://www.robh.nl/)

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to