| Subject: | Re: proposed I2C interface | |
|---|---|---|
| From: | Ron Goldman (Ron....@sun.com) | |
| Date: | Dec 13, 2008 7:05:54 pm | |
| List: | net.java.dev.spots.dev | |
Refine Search
| From | Sent On | Attachments |
|---|---|---|
| Ron Goldman | Dec 13, 2008 2:52 pm | |
| Eric Arseneau | Dec 13, 2008 3:57 pm | |
| Ron Goldman | Dec 13, 2008 4:21 pm | |
| Robert Alkire | Dec 13, 2008 6:41 pm | |
| David G. Simmons | Dec 13, 2008 7:00 pm | |
| Ron Goldman | Dec 13, 2008 7:05 pm | |
| Ron Goldman | Dec 13, 2008 7:57 pm | |
| David G. Simmons | Dec 14, 2008 6:09 am |
| Subject: | Re: proposed I2C interface | |
|---|---|---|
| From: | Ron Goldman (Ron....@sun.com) | |
| Date: | Dec 13, 2008 7:05:54 pm | |
| List: | net.java.dev.spots.dev | |
On Dec 13, 2008, at 7:01 PM, David G. Simmons wrote:
I'd actually like to see the TWI stay in the method names. openTWI(), closeTWI(), readTWI() and writeTWI() instead of just open() close() read() write(). Likewise probeTWI() and isTWIBusy()
I think it makes it more clear to us idiot-users what, exactly, we're doing.
David,
Yeah I considered that, but since the calls will need an II2C instance what you'll see is:
II2C i2c = Spot.getInstance().getI2C();
i2c.open(); i2c.read(temp, data, 0, 1);
etc. Does that seem enough context? Or do you still want the I2C in the method name?
-- Ron --

