Since Easter, when I promised a new release of this software, I’ve been exceptionally busy in a money-earning sort of way. I’ve noticed that others are blogging less now that their business has (presumably) picked up, so I’m not alone in disappointing my readers, but that is no excuse and so I have just uploaded the software I promised. Read more…
The free software you may have downloaded from this site embodies an error of principle (details another time). It compiles with VC++ and IAR (ARM), and the code is correct and runs properly. However, I tried g++ today and it was less forgiving. Unfortunately, it’s right and I’m wrong, even though I got away with it up to now. I’m working on a fix and will post again when I have finished it.
The C++ dynamic memory software I published last week has been updated with a small but useful enhancement.
Find out more by downloading it: start by going to the Subscribers’ page.
For the last couple of months, my software efforts have been diluted by the need to attend to other matters no less important but somewhat distracting. Now I have finally released some software. It is not the whole of SKC++, though. I learned so many things, at a detailed level (mainly about C++), in developing SKC++ that I realised that I had built “one to throw away”, as the saying goes. The refactoring is well underway and I have decided initially to release some of the essential elements of SKC++ in stages, as library modules which can be used more generally Read more…
Following on from previous postings, here is a UML diagram showing two classes concerned with dynamic memory handling: Read more…
Today’s post is about the strategy of dynamic memory handling in SKC++.
Last time, I recommended a short slide presentation for perusal. I will not repeat here what that says, except to quote the last slide:
Preventing fragmentation
• Always use pools, never heaps
– Exception: memory which is never intended to be freed can be taken from a heap
• Override the global new() and delete() operators
• Consider per-class new() and delete() operators
– Quicker, as well as safer
In a nutshell, that is the strategy for SKC++. Read more…
Today, I am working on the dynamic allocation scheme for SKC++. It’s very simple (as everything is supposed to be in SKC++), so it won’t be long before I post again, reporting on progress.
In the meantime, if you’re wondering what’s wrong with using the standard new and delete mechanisms that come with C++ I urge you to have a look at my short slide presentation on the subject. The last two slides are particularly important.
Till soon…