>
>
> > BTW, remember the discussion about having two i2c hw slave lib ? One for
> > init, read and write procedure, another fir the ISR handling ? Note in my
> > blog posts (part 2), I define my own ISR, by enabling Start/Stop
> interrupts.
> > This couldn't be possible if ISR was in the same lib as the init
> procedure.
> > Flexibility... :)
> Maybe we should put serial_hw_init() also in a separate file ? ;) ;)
That's an idea ! More seriously, since ISR aren't explicitly called, when
you import a lib with a ISR defined in it, you can't deactivate it, even
ignore it.
> > OK, ("Phew, I thought it was something else :)")
> Now I wonder... What did you think?
I prefer not to reveal it :)
Seb
--
Sébastien Lelong
http://www.sirloon.net
http://sirbot.org
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
