There is an optional board param than may be passed in the constructor opts for all device classes. Simply put, it allows the user to specify which board they want to use in projects that have multiple boards. It is currently not documented anywhere and should probably be added to all the classes.

I'm following https://gobot.io/documentation/platforms/chip/ on macOS and seeing a compilation error in the sample program:

undefined: gobot.On

Repro steps

I ran go get -d -u gobot.io/x/gobot/... (worked)

Pasted the sample listed to main.go:

package main

import (
    "fmt"

    "gobot.io/x/gobot"
    "gobot.io/x/gobot/drivers/gpio"
    "gobot.io/x/gobot/platfor

There are a few flags that currently don't have proper error checking. The ones I found are -gc, -scheduler and -size. Using the wrong value will lead to no or unexpected errors.

I think the best way to handle it is to add a new method to compileopts.Config that checks whether there are any faulty flags, which is then called from the main function.

a detailed documentation is missing about WebServer example "HelloServer.ino":
what is #include <ESPmDNS.h> for?
what is void handleRoot() for?
what is void handleNotFound() for?
what is server.on("/", handleRoot) for?
what is server.on("/inline", ) for?
what means: server.send(200, "text/plain", "this works as well");
(i.e., as well to what?)
what is server.onNotFound(handleNotFo

Solutions

1. Convert INO files to CPP

2. Manual prototype declaration

#ifdef DO_NOT_USE
typedef int32_t delaytype;
void thisShouldNotAppearInTheBinary(delaytype timer); // aded manually
void thisShouldNotAppearInTheBinary(delaytype timer) {
  delay(timer);
}
#endif

I'll get this added to the documentation shortly, but in the meantime here is a list of some relevant issues and comments which I'll use for it:

SmingHub/Sming#1992 (comment)
SmingHub/Sming#1724 (comment)
#2002

Do you have any explanation or reference for this formula?
https://github.com/mysensors/MySensors/blob/f4fd69eb131cd5df5572bc9018d3aa2245020123/examples/DustSensorDSM/DustSensorDSM.ino#L136

e.g. the demo implementations in this sub-directory
https://github.com/particle-iot/device-os/tree/v1.3.0-alpha.1/user/tests/app/ble
or some code snippets in the docs and tutorials still use #include "application.h".

Although Particle.h (formerly Spark.h) should have replaced application.h (as per #249) we keep finding internal/official code using application.h while we try to get t