'Sets of Fields' is a concept that fears them young 'un assembler programmers as this is what happens when IBM gets creative. If you run out of places to put stuff then you can take something known and make it mean more things. That's where sets of fields become important. Now you can look at a variable and it will start with a number that tells you how many pieces of information are in it. IBM did this all over the place and it was brilliant as it was a mechanism for downward compatibility and it was incredibly effective.
So what's the point of any good idea?
(Ed: steal it?)
Right you are.
The pondering is over whether it will be necessary to handle a painting being in multiple shows. I'm thinking it's inevitable. It hasn't been mentioned but I know that's true already. What I don't know is whether it's important.
I believe I've already made up my mind to write it but I review for a bit the value of it. Correcting the problem with the show displays turned into Godzilla versus the Smog Monster but the code ended up the better for it ... so ... screw it up with yet another change.
Programmers may scoff and say, pfft, that's just an array. I can program that in one line of code. Yes, of course you can, precious little snowflake, but let's see you do it with two index registers and an accumulator (Motorola 6502). If that's too much then let's try IBM as you'll get (gasp) sixteen registers now. Even though to the juniors assembly language programming is like computer paleontology, it still has merit and, what's more, these dinosaurs are still alive and today they are bigger than they ever were.
So what's the point of any good idea?
(Ed: steal it?)
Right you are.
The pondering is over whether it will be necessary to handle a painting being in multiple shows. I'm thinking it's inevitable. It hasn't been mentioned but I know that's true already. What I don't know is whether it's important.
I believe I've already made up my mind to write it but I review for a bit the value of it. Correcting the problem with the show displays turned into Godzilla versus the Smog Monster but the code ended up the better for it ... so ... screw it up with yet another change.
Programmers may scoff and say, pfft, that's just an array. I can program that in one line of code. Yes, of course you can, precious little snowflake, but let's see you do it with two index registers and an accumulator (Motorola 6502). If that's too much then let's try IBM as you'll get (gasp) sixteen registers now. Even though to the juniors assembly language programming is like computer paleontology, it still has merit and, what's more, these dinosaurs are still alive and today they are bigger than they ever were.
No comments:
Post a Comment