Question 1

I use C++, why use TinyCLR OS instead?

greg · Accepted Answer

C and C++ languages are the “go to” languages when it comes to microcontrollers. In fact, the entire TinyCLR OS is built using C and C++. The problem is that the code is non-portable between systems, there is no run-time error checking, and the tools for compiling and debugging on a commercial level are very costly.

Question 2

I use C++, why use TinyCLR OS instead?

greg · Accepted Answer

C and C++ languages are the “go to” languages when it comes to microcontrollers. In fact, the entire TinyCLR OS is built using C and C++. The problem is that the code is non-portable between systems, there is no run-time error checking, and the tools for compiling and debugging on a commercial level are very costly.

Question 3

I use C++, why use TinyCLR OS instead?

greg · Accepted Answer

C and C++ languages are the “go to” languages when it comes to microcontrollers. In fact, the entire TinyCLR OS is built using C and C++. The problem is that the code is non-portable between systems, there is no run-time error checking, and the tools for compiling and debugging on a commercial level are very costly.

Question 4

I use C++, why use TinyCLR OS instead?

greg · Accepted Answer

C and C++ languages are the “go to” languages when it comes to microcontrollers. In fact, the entire TinyCLR OS is built using C and C++. The problem is that the code is non-portable between systems, there is no run-time error checking, and the tools for compiling and debugging on a commercial level are very costly.

Question 5

I use C++, why use TinyCLR OS instead?

greg · Accepted Answer

C and C++ languages are the “go to” languages when it comes to microcontrollers. In fact, the entire TinyCLR OS is built using C and C++. The problem is that the code is non-portable between systems, there is no run-time error checking, and the tools for compiling and debugging on a commercial level are very costly.