Pinetime VS C++ Middleware Writer

You can check a popular firmware for it at https://github.com/JF002/InfiniTime which has apps for Android, iOS and Linux.

And already a new release, 1.6.0 https://github.com/JF002/InfiniTime/releases/tag/1.6.0

There was an InfiniTime release today that keeps the time when the watch is reset, and hopefully fixes some connection issues: https://github.com/JF002/InfiniTime/releases/tag/1.5.0

When I first bought my PineTime, which incidentally is pretty darn cheap and open source, I found out that it and a lot of similar devices are accessed over BlueTooth with a thing called GadgetBridge:

I only have used my watch for a couple of days and it doesn't seem to happen for me with a samsung s10 and Gadget bridge. But there are a couple of issues open on github relating to this problem, you could take a look at those. here is one that seems related https://github.com/JF002/InfiniTime/issues/302

I use unique_ptr, but not as much as I used to. I've never used shared_ptr. This is my library that uses some C++ 2020 and 2017 features.

I started with Linux in the late 90s. I switched to FreeBSD around 2013 and returned to Linux a couple of years ago. Io_uring was the main reason I had to come back. At first I ported the back tier of my code generator back to Linux and then I ported the middle tier from being POSIX based to Linux.

Are there others that minimize multithreading and opt for multi-processing with single threaded processes? Call me a simpleton, but this approach eliminates some of the most difficult bugs by design. Here's an example of one of my single-threaded servers. The network io is asynchronous, but the file io is synchronous. Thanks

I've been working on this program for 13 years now. At one point it had 7 global variables and none of them were const. Now it has 4 global variables and 2 of them are const.

in one of my programs. I'm thinking about changing it to:

It's a merger of services and code generation: an on-line code generator that outputs low-level messaging and serialization code based on high-level input. It's implemented as a 3-tier system and uses output from the code generator in each tier. There's also a traditional library that's part of the repo.

Support for more data types for message lengths. Previously message lengths were always 4 bytes. I used this, for example, to reduce the size of the type used for message lengths between the front and middle tiers of the CMW from 4 bytes to 2 bytes.

More concretely, I use it to generate code that's used in each of the tiers mentioned above. The link is to one example of that.