Stacks of problems
In computing, a stack is a list of things, where you can only take off the most recent thing that you have put on. Just like a real stack of items.
This week has been a bit like that with the different bugs and issues I’ve had to work through.
I started off trying to write some code to decode a function name from an address, using the APIs available within Carbide.c++. Then I discovered that Carbide.c++ doesn’t tell Eclipse to load modules in the normal way, so I had to work around that. My workaround revealed that Carbide.c++ appears to be doing something odd with parsers, too, so I had to download Nokia’s modifications to CDT to discover what. Upon downloading that, I discovered that they’ve provided their changes in a format which required me to install a tiny programme to use them. Installing the programme simultaneously upgraded lots of other programmes, which filled up my hard disk, so I had to move some big files to another hard disk. Then the programme that used those files would no longer work.
I can only solve each of these problems one at a time, in reverse order, before I go back to the previous problem. Eventually I’ll make my way back down the stack to the original problem I was trying to solve.
So, that’s what a stack is.
(Also I have found that Nokia’s uploaded patches appear to correspond to a prior version of Eclipse, so even now I’ve got patching working, they won’t apply cleanly. Grumble grumble.)