fenichelar / pin Goto Github PK

So, as for using pins_arduino.h... everyone else does... Why not here? Makes it "just work" - for any platform (AVR-only, at this point, I'd guess) that has an existing pin mapping definition. This format does work, but is cryptic and reinvents the wheel. Is there a reason for it (i.e.. you need the user to tell you where the registers are, etc?)

I do not see any way to analogWrite(). Am I wrong? Why the omission?

Why are there two sets of functions/variables for state and value? Are they not he same thing (HIGH/LOW)?

If I ever tried to define the object first and try to initialize the object later.

say...

Pin ledPin;

it will result in a compiler error "no matching function for call to Pin::Pin()
because it doesn't have a default constructor...