Slitherine

quote:

ORIGINAL: larryfulkerson

you are absolutely correct. Thanks for fixing my post.

EDIT: On second thought, lemme explain why I wrote it that way originally. When a programmer is writing a program from scratch for
the first time he/she usually has an idea what it's supposed to do and can plan ahead for which variables do what and what functions
are going to be needed to do what etc. And he/she can usually make a reasonably good first draft. The bugs are typos, for loop
off by one, and usually simple things that go wrong and not usually logic errors.

And then comes the need to change a program, which is sometimes a different programmer than the original author and he/she usually
doesn't have a clue what the program was written for, what it's supposed to originally do, what the variables are, what functions there
are and has to "learn" the program by trial and error.

You can tell from what I've written above how long ago I used to write programs and how much has changed since. Object orientation
came along during my later years and I had to re-learn how to program using the object oriented method, which I'm grateful for
because I learned a lot about variable isolation, "method" evolution, and so on. It was a great trip.

quote:

ORIGINAL: witpqs
I'm with you, Larry! In high school I started working in IT as a computer operator during the summers. RCA Spectra 70/60 36-bit mainframes, IIRC. There were times when we had to patiently explain to a newly hired programmer that a card reader (roughly the size and shape of two and a half washing machines side by side) could not be written to as it was a read-only device. Showing them usually helped, including lifting the cover to reveal the movements (and lack of any punch mechanisms).

quote:

ORIGINAL: witpqs

quote:

ORIGINAL: larryfulkerson

you are absolutely correct. Thanks for fixing my post.

EDIT: On second thought, lemme explain why I wrote it that way originally. When a programmer is writing a program from scratch for
the first time he/she usually has an idea what it's supposed to do and can plan ahead for which variables do what and what functions
are going to be needed to do what etc. And he/she can usually make a reasonably good first draft. The bugs are typos, for loop
off by one, and usually simple things that go wrong and not usually logic errors.

And then comes the need to change a program, which is sometimes a different programmer than the original author and he/she usually
doesn't have a clue what the program was written for, what it's supposed to originally do, what the variables are, what functions there
are and has to "learn" the program by trial and error.

You can tell from what I've written above how long ago I used to write programs and how much has changed since. Object orientation
came along during my later years and I had to re-learn how to program using the object oriented method, which I'm grateful for
because I learned a lot about variable isolation, "method" evolution, and so on. It was a great trip.

I'm with you, Larry! In high school I started working in IT as a computer operator during the summers. RCA Spectra 70/60 36-bit mainframes, IIRC. There were times when we had to patiently explain to a newly hired programmer that a card reader (roughly the size and shape of two and a half washing machines side by side) could not be written to as it was a read-only device. Showing them usually helped, including lifting the cover to reveal the movements (and lack of any punch mechanisms).

HELLO    CSECT               The name of this program is 'HELLO'
*                            Register 15 points here on entry from Op/sys or caller.
         STM   14,12,12(13)  Save registers 14,15,and 0 thru 12 in callers Save area
         LR    12,15         Set up base register with programs entry point address       
         USING *,12          Tell assembler what register we are using for pgm. base
         LA    15,SAVE       Now Point at our own save area
         ST    15,8(13)      Set forward chain
         ST    13,4(15)      Set back chain               
         LR    13,15         Set R13 to address of new save area
*                            -end of housekeeping (similar for most programs) -
         WTO   'Hello World' Write To Operator  (Operating System macro)
*
         L     13,4(13)      restore address to caller-provided save area                     
         LM    14,12,12(13)  Restore registers as on entry
         SR    15,15         Set register 15 to 0 so that the return code (R15) is Zero
         BR    14            Return to caller
*           
SAVE     DS    18F           Define 18 fullwords to save calling program registers 
         END  HELLO          This is the end of the program         

quote:

ORIGINAL: larryfulkerson

Here's a display of the ships that were damaged by the Allied guns at Cebu and the extend of the damage. But I really needed to
deliver some supplies to the troops there so the war could continue.