In response to one of the Google+ comments (which can be found here) to my post on how to create a Tensor class, I have decided to write an article on how to modify the
CTensor to use a storage class which uses automatic allocation on the heap or the stack depending on whether a stack overflow is likely.
This is quite a long post, so I’ve provided a table of contents here for easier navigation:
Posted by Thomas Russell on 14 January 2015
- How does automatic allocation help us?
- Writing our automatic storage class
- Finishing the stack-allocated class
- Finishing the heap-allocated class
- The Indexing Operator (
- Conclusion Read more »
I recently got a Pebble as a present from my lovely girlfriend and I’ve been toying with the idea of creating an app for it, partly for fun and partly to support the awesome work that I think the guys at Pebble are doing.
I’m aiming to help resolve what I feel is one of the major issues with the Pebble framework at the moment, which is its fixed address app structure. For those who don’t know; you can currently only install a maximum of 8 apps/watchfaces on the watch at any one time regardless of how much space each app or watchface takes up, this means that whilst your Pebble has a storage capacity of 800KB, the majority of that space is likely wasted.
The primary goals of the app can be summarized as follows: Read more »
Posted by Thomas Russell on 13 December 2014