Follow Us
Categories
Archives
- February 2024
- January 2024
- August 2023
- December 2022
- November 2022
- October 2022
- February 2022
- October 2021
- September 2021
- August 2021
- July 2021
- June 2021
- May 2021
- January 2021
- November 2020
- October 2020
- August 2020
- April 2020
- February 2020
- January 2020
- October 2019
- September 2019
- July 2019
- May 2019
- April 2019
- March 2019
- February 2019
- January 2019
- December 2018
- October 2018
- September 2018
- August 2018
- July 2018
- April 2018
- February 2018
- January 2018
- December 2017
- November 2017
- October 2017
- September 2017
- August 2017
- July 2017
- June 2017
- May 2017
- April 2017
- March 2017
- February 2017
- January 2017
- December 2016
- November 2016
- October 2016
- September 2016
- August 2016
- July 2016
- April 2016
- January 2016
- December 2015
- November 2015
- October 2015
- September 2015
- August 2015
- July 2015
- June 2015
- May 2015
- January 2015
- December 2014
- November 2014
- October 2014
- September 2014
- August 2014
- July 2014
- June 2014
- May 2014
- April 2014
- March 2014
- February 2014
- January 2014
- November 2013
- September 2013
- August 2013
- July 2013
- June 2013
- May 2013
- April 2013
- February 2013
- January 2013
- November 2012
- October 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- December 2011
- November 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
Author Archives: Glennan Carnie
Technical debt
What is it & how does it affect software engineering management?
The ‘Golden Triangle’ of project management
The ‘golden triangle’ of project management uses the following constraints:
The rule is: you can pick any two of three; you can’t have them all.
When it comes to software development projects, it’s not uncommon to have a fixed time to market and budget, which means that, under pressure, the constraint that’s affected is quality.
Commonly, when the project management refers to ‘quality’ it implicitly means Intrinsic Quality.
Intrinsic […]
Your handy cut-out-and-keep guide to std::forward and std::move
I love a good ‘quadrant’ diagram. It brings me immense joy if I can encapsulate some wisdom, guideline or rule-of-thumb in a simple four-quadrant picture.
This time it’s the when-and-where of std::move and std::forward. In my experience, when programmers are first introduced to move semantics, their biggest struggle is to know when (or when not) to apply std::move or std::forward. Usually, it’s a case of “keep apply std::move until it compiles”. I’ve been there myself.
To that end I’ve put together a […]
Posted in C/C++ Programming
Tagged C++, C++0x, C++11, C++1y, Modern C++. C++11. C++14, move policy, move semantics, resource management
2 Comments
“May Not Meet Developer Expectations” #77
Posted in C/C++ Programming
Tagged C++11, C++14, debugging, declaration, Modern C++, multi-threading
3 Comments
Exceptional fun!
In this article I want to look at some applications for one of C++’s more obscure mechanisms, the function
Posted in C/C++ Programming
Tagged C++03, C++11, C++14, exceptions, function try-block, goto, Modern C++
3 Comments
Making things do stuff – Part 9
As a final instalment in this series on hardware manipulation I thought I’d revisit read-only and write-only register types.
Using tag dispatch is not the only way to solve the read- or write-only Register problem. For completeness let’s explore two other alternatives – SFINAE and constexpr if.
For these examples I’m going to use a simplified version of our Register class. I’m ignoring the bit proxy class and using a reduced API. Once understood, the techniques below can be applied to these […]
Posted in C/C++ Programming, Design Issues
Tagged C++, C++0x, C++11, C++1y, constexpr-if, GPIO, hardware manipulation, Modern C++, SFINAE, tag dispatch, Templates
1 Comment
Making things do stuff – Part 8
We’ve been using templates to provide a hardware register abstraction for use with hardware manipulation problems, typical of what you’d find in a deeply-embedded (“bare-metal”) system.
Previously, we looked at using trait classes to establish pointers and tag-dispatch to handle special-case registers, such as read-only or write-only register.
In this article we’re going to add some syntactic sugar to our Register class, to allow the developer to access individual bits in the register using array-index ([]) notation. This will allow us to […]
Making things do stuff – Part 7
In our previous article we explored using templates to build a generic ‘register’ type to allow programmers to access hardware without all the nasty syntax of integer-to-pointer casting, etc.
At the moment, this class gives us little extra functionality beyond cleaning up the syntax (although, in its favour, it also doesn’t incur any additional run-time cost/performance).
In this article we’re going to extend our design to consider special hardware register types – notably read-only and write-only registers – and see how we can […]
Posted in C/C++ Programming
Tagged C++, C++0x, C++11, C++1y, hardware manipulation, Modern C++. C++11. C++14, Templates
2 Comments
Making things do stuff – Part 6
As code designers we tend to eschew specific ‘stove-pipe’ code in favour of reusable code elements. Up until now we’ve been coding some very specific examples so it’s probably worth looking at some more generic solutions.
In this article we’ll look at building generic register manipulation classes (or, as one commenter referred to them, ‘register proxy’ classes). Here, we’re really exploring code design rather than coding ‘mechanics’. I’m using this to explore some factors like the balance between efficiency, performance and […]
Posted in C/C++ Programming
Tagged C++, C++0x, C++11, C++1y, GPIO, hardware manipulation, Modern C++. C++11. C++14, Templates
3 Comments
Making things do stuff – Part 5
We’ve been looking at using C++ to manipulate I/O hardware. Previously, we’ve looked at the fundamentals of hardware manipulation; and how to encapsulate these mechanisms into classes. If you’ve not been following along I’d recommend reading the previous articles first before continuing.
This time we’ll explore a lesser-known feature of C++ and its application in hardware manipulation – placement
Posted in C/C++ Programming
Tagged C++, C++0x, C++1y, hardware manipulation, IO, placement new
3 Comments