Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@ tags:
|68| PA1| CANRX| 3| 6|
|69| PA0| CANTX| 15| 9|
|70| PA17| SDA1| 3| 6|
|71| PA18| SCL2| 15| 9|
|71| PA18| SCL1| 15| 9|
|72| PC30| LED "RX"| 15| 9|
|73| PA21| LED "TX"| 3| 6|
|74| PA25| (MISO)| 15| 9|
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ This is a style guide to writing library APIs in an Arduino style. Some of these
**Use the established core libraries and styles.**

* Use `read()` to read inputs, and `write()` to write to outputs, e.g. `digitalRead()`, `analogWrite()`, etc.
* Use the `Stream` and `Print` classes when dealing with byte streams. If it’s not appropriate, at least try to use its API as a model. For more on this, see below
* Use the [`Stream`](https://www.arduino.cc/reference/en/language/functions/communication/stream/) and `Print` classes when dealing with byte streams. If it’s not appropriate, at least try to use its API as a model. For more on this, see below
* For network applications, use the `Client` and `Server` classes as the basis.
* Use `begin()` to initialize a library instance, usually with some settings. Use `end()` to stop it.
* Use camel case function names, not underscore. For example, **analogRead**, not **analog_read**. Or **myNewFunction**, not **my_new_function**. We've adopted this from Processing.org for readability's sake.
Expand Down