Badly done, IMHO. You should own it even as a "failure" and keep it around somewhere, even if just as an example of how things should NOT be done.
Even (or specially) bad code can be a very useful didactic resource: most students will look at it and maybe laugh a little at its clumsiness in public ... but privately they will think "Wow! I was about to do exactly that! Thank the gods I saw it in time!", and it'll at least have served a purpose as an aid in learning.
Never thought of that, thanks. I learn the right attitude from you- own it as a failure. Nevertheless, I think I will be able to rewrite the code with minor improvement if I want to.
For example, I will use Cardinal for DWORD, and Array [1..2] of Cardinal for 4-byte address and 4-byte size. However, I am not sure how the Cardinal will be stored in binary - MSB and LSB in reversed order?
I is here: http://pascal.hansotten.com/per-brinch-hansen/
OMG
, you're an expert. I am speechless, the book(s) are free!