C++ object orientated library extensions

[sstaub]

There should exist a c++ object orientated API for Digital, Analog , SPI, I2C, UART...
e.g. for GPIO

class Digital {
	public:
		Digital(uint8_t pin, uint8_t mode);
		~Digital();
		void write(bool value);
		void toggle();
		bool read();
	};

[aentinger]

Good Morning @sstaub ☕ 👋

Why do you think so? (This not meant to discourage the contribution, but rather an invitation to hear your reasons why you believe such an API should exist.)

[sstaub]

You really want to start a basic discussion of pro and cons of OOP?

[aentinger]

No and no need to get belligerent 😉. I want to hear why you think that this belongs into the Arduino API.

[sstaub]

A C++ API makes code more readable, also avoiding pre processor directives for identification.
You can do a simple blink the classic way:

#define LED1 LED_BUILTIN
void setup() {
  pinMode(LED1, OUTPUT);
}

void loop() {
  digitalWrite(LED1, HIGH);
  delay(1000);
  digitalWrite(LED1, LOW);
  delay(1000);
}

or more elegant:

Digital led1(LED_BUILTIN, OUTPUT);
void setup() {
}

void loop() {
  led1.write(HIGH);
  delay(1000);
  led1.write(LOW);
  delay(1000);
}

[sstaub]

I don't think that are any problems with copyright of the API, there is none. Yes, many things on threading are not easy, because the whole Arduino system must be thread safe, lot of work.

[PaulStoffregen]

"Untold History" is supposedly just about an API, which if subject of copyright was supposedly LGPL licensed. But Untold History was really about negative PR meant to assist Federico Musto who was trying to take over Arduino at that time. Musto in turn offered Hernando Barragán a position as Arduino Chief Design Architect.

[sstaub]

I can remember that Oracle lost the fight about copyright of the Java API. In Europe it is not possible to get a copyright for a simple API.
But I want to stop the discussion at this point, it leads to nowhere.

[PaulStoffregen]

The point is you're essentially saying Arduino should adopt an API proposal from a man who participated in a negative PR stunt intended to harm public reputation of some of Arduino's founders during a time of conflict between parties for control over Arduino. Even if copyright isn't issue, even if Arduino did unfairly fail to credit his work, the fact remains that he didn't make any good faith effort communicate his attribution concerns to Arduino but rather participated in a harmful PR attack meant to hurt Arduino's public reputation. That attack essentially claims Arduino used his work without (sufficient) attribution. And now you're saying Arduino should make even more use his API proposals!

[sstaub]

The Wiring++ API is only one idea of possibility, I never said this is the one Arduino should do, only think about. Read my first posts of this thread. And I think there should more respect for the inventor who have the idea of "Arduino/Wiring".

[sstaub]

I know mbed and I worked with it for while, this is one of the reasons. The idea was also a part of Wring++ which was never released. The OOP API is thought as an extension not at replacement.