I didn’t work on Hamurabi today, so I won’t be writing about that. In fact, I won’t be writing any actual code for it until the books on Pascal come in.
I will be starting on some pseudo code. When I work on programs, I found that if I write it down in English, in an outline form, I can then break each piece down into logical steps. I then just keep breaking each step down until they are manageable.
I’ve been thinking about doing Hamurabi in ZBasic at the same time, using the same pseudo coding.
I may also do a straight conversion to Applesoft.
I spent the day working on other projects. Right now, my Apple //c is tucked away into a corner off the end of my desk (See the picture above). It’s not really a good place to work on it, but has worked out well for small Apple II projects in the past. I’m coming to the conclusion, that I need to move it in order to make it more useful.
Non-Apple II stuff follows.
So yesterday, I wrote about Windows doing an update. This was not entirely acurate as it was only my laptop, running Windows 7 32bit. This morning my desktop, Win 7 64 bit, my old desktop Win XP and my other laptop running Ubuntu, all went through an update that required a restart. The Win 7 desktop had to be restarted again in order to get back on the internet.
The older desktop I caught just before the update restarted. This desktop runs SimH, simulating a DEC PDP 11/70 with RSTS/E V7. When the computer shuts down, without shutting down SimH properly, it takes a while to restart SimH.
Ah yes, flow-charting and pseudo-code! Two time-tested traditions! I still write my design notes on paper, using diagrams as appropriate. I always make sure to date my notes so I can maintain a good chronology.
Flow charting… Arg… I do only a most informal flow chart when I’m desperate.
We used to have to do those for every program we wrote in our programming classes.