Hi,

I can't deliver my 2 cents, so I'll pay 1 cent interest below ;-)

Or to put it in other words: I don't have an consistend view on this
topic. There is however one thing that I concider important, and I
want to share with you (again):

Some libaries provide similar functionality in different ways, like in
hardware + software (or for serial, even hardware implementations with
and without flow control).
And both examples have something else in common: chuncks of code are
build on top of it are often reusable that call the libs from many
point within that chunck. For example a menu on a serial port or a
procedure that writes a block to an eeprom (and deals with blocks size
and address).

Of course can't have those libraries (that provide similar
functionality in different ways) exact the same interface because this
would limit all future enhancements. But they do at least share a set
of basic interfaces.
It is valueble to keep the name of this common interface the same, so
adaption of the code chunck mentioned is reduced to the minimum.

For i2c hardware and software I implemented it this way. Consequence
is that it's not so easy to use them both at the same time, but this
disadvantage is much less then the possibility to change the
underlaying lib with litte adaption.

Similar, I want to have the same interface on all serial libs. And
probably als on lcd libs.
I can imagine this is less relevant for temperature sensors, because
the interaction is less complex: each sensor is read at one place in
the program and the result is taken for processing. So switching
library only requires limited changes in the main program.

Joep

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