Would it be useful to have a database of library conflicts? Users could report problems and if conflicts are confirmed they could be included in the database to avoid others having to discover the conflicts all over again.
The most cases i.e. "library conflicts" caused by bad user code, I think.
The cases of real library incompatibility are very rare and are usually associated with an attempt to use the same hardware resource (for example, a timer or an interrupt vector) by two libraries.
Sure. But how would beginners learn about it and who would maintain it?
Most seasoned forum members recognize the typical library conflicts, like SoftwareSerial and Servo, and can alert newcomers quickly.
And then you have the problem of multiple libraries with the same or extremely similar names, like LiquidCrystal.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.