I'd like to get some input on this interface and a little feedback on how to make it stronger or more clear.
Kwatters said the pinEnable(String pin) method in Arduino is confusing.
I added this method because previously he said he wanted to pinEnable(D0) .. I guess I thought he meant pinEnable("D0") .. which currently works, but I'm not a big fan ..
I'd be fine removing pinEnable(String) .. but I'd like us to agree what would be the alternative to use in Python.
Some find the 'real' address disagreable, because its clearly documented what the value is : e.g. pin 14 is A0 on an Uno.
Plan is to get rid of pinEnable(String) in Arduino and all pin as String methods,
And make a bunch of constants ?
Constant ints would be ok .. public static final int D0 = 0; .. public static final int A0 = 14;
but in Python it would look like this - which is rather verbos, but ok by me...
Let me know your thoughts and opinions...