Martino Facchin

Hi @schnoberts1 , can you paste the crash output? We never tried compiling with gcc > 10 so it might be some new optimization kicking in.

Definitely agree on the concept. On the numbering, it really depends on the expected pattern to consume these values. Eg: `while (!can.write())` could mean "keep trying until the error disappears",...

What about adopting `Print` strategy and add [`setWriteError/getWriteError`](https://github.com/arduino/ArduinoCore-API/blob/4a02bfc0a924e1fec34c3bb82ffd5dfba7643a0c/api/Print.h#L47C9-L47C22) while returning `0` on failure?

Hi @Parsec86 , you are probably missing the udev rules https://github.com/arduino/ArduinoCore-mbed/blob/master/post_install.sh that should install automatically with the core. We don't use the drag and drop for uploading but the raw...

Hi @pdmartinson , can you post a simple sketch that we can use to reproduce the issue? Eg. try removing some functions (even if the sketch doesn't do anything useful...

Hi @swanjeng , the `while (!Serial)` pattern was introduced to allow in fact USB native ports to enumerate before trying to print (on nowhere). On native UART-to-USB like UNO R4...

As @kevans91 perfectly stated, the problem with jni libs is that they are intended to be "included" in the class / library (so in the resulting jar) they are targeting....

Hi @Floessie , I moved the issue to `arduino-cli` since the builder repo is now just a "frontend" for the cli . The problem here is that spurious prototypes are...

I think I got it (more or less). The generated prototypes are inserted just above the first function implementation. In this way, `template Command getCommand(...` is being declared before `template...

The official way to avoid the preprocessor dance is to rename all "expert" files to `.cpp`. The preprocessor only fires on `.ino` but that file can simply be an empty...