I've been thinking a lot about the potential of the Teensy 3.5 & 3.6, and their potential for preemptive schedulers. I've written such schedulers in the past on microprocessors with less capabilities than these devices, and I'm planning to do this again with the new Teensies.
I believe a part of our future lies in multi-threading. These processors are too capable to hold them to a single thread.
I've been eyeing the IntervalTimer class (here only as an example) and thinking about the changes I'll have to make to make it thread-safe, or to be able to use it as a base class for something that is thread-safe.
My suggestion is that you keep in mind thread-safety while writing or updating library code. There's generally little cost in making a bit of code thread-safe, and we can hide this cost in the big jump in T3.6/3.6 processor speed. While there would be little return on your time now it might make life simpler in the future.
I wish there were a place to save for general use thread-safe conversions. I don't want to create two sets of code that need to be maintained...
I believe a part of our future lies in multi-threading. These processors are too capable to hold them to a single thread.
I've been eyeing the IntervalTimer class (here only as an example) and thinking about the changes I'll have to make to make it thread-safe, or to be able to use it as a base class for something that is thread-safe.
My suggestion is that you keep in mind thread-safety while writing or updating library code. There's generally little cost in making a bit of code thread-safe, and we can hide this cost in the big jump in T3.6/3.6 processor speed. While there would be little return on your time now it might make life simpler in the future.
I wish there were a place to save for general use thread-safe conversions. I don't want to create two sets of code that need to be maintained...