Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Fortran : 1st program 1954, Sept 20

Fortran : 1st program 1954, Sept 20

Scheduled Pinned Locked Moved The Lounge
comdata-structuresquestion
24 Posts 16 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C Chris Nic

    After university, I worked in a mining company which had a CDC 7000. I remember that it had a file system called LISA (Linked Access Sequential Access I think it meant). When they upgraded to a CDC Cyber something it was fantastic. We used to compile the program and then do the fine tuning in the assembly output to get speed. That was the time when we used manual stop watches to measure the speed of a program when we tried to get the best time possible, a couple of seconds more or less didn't make a difference.

    D Offline
    D Offline
    dshillito
    wrote on last edited by
    #14

    In programming the CDC 6600 I also used to recode the innermost stuff in assembly language for speed. Time on our system was charged by the second. High priority jobs were scheduled immediately but cost 50c per second. That was in 1973 when my entry-level job paid $6000 per year, so it is more like $5 per second today. The compilers were not as good as optimizing as today's compilers so a good recode in assembly language could result in a 10x speedup, i.e. a 10x reduction in cost. In addition there was a charge for the number of I/O operations but there was also a multiplier for the field-length (the amount of main memory you were using at the time of the I/O) since the job tied up main memory due to the I/O buffers needing to be fixed during the transfer. This meant it was also very beneficial to structure a job to reduce its memory utilization to the absolute minimum during an I/O phase and expand it to the maximum during a CPU-bound phase. Again there was the possibility for 10-fold reductions in cost.

    1 Reply Last reply
    0
    • R raddevus

      Very geeky Foxtrot comic for Fortran celebration! https://i.stack.imgur.com/TKkXL.jpg[^] Sept 20, 1954 the first Fortran program was run. On this day 09/20 – Manning[^]

      T Offline
      T Offline
      Tomz_KV
      wrote on last edited by
      #15

      It seemed that the language was created before computer was invented.

      TOMZ_KV

      T 1 Reply Last reply
      0
      • T Tomz_KV

        It seemed that the language was created before computer was invented.

        TOMZ_KV

        T Offline
        T Offline
        theoldfool
        wrote on last edited by
        #16

        [^]

        >64 If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.

        1 Reply Last reply
        0
        • R raddevus

          Very geeky Foxtrot comic for Fortran celebration! https://i.stack.imgur.com/TKkXL.jpg[^] Sept 20, 1954 the first Fortran program was run. On this day 09/20 – Manning[^]

          O Offline
          O Offline
          OldGeezer
          wrote on last edited by
          #17

          If you run this on a CDC 6400 class machine it will print 2 which was both fun and educational :) PROGRAM ONETWO CALL ADDONE(1) PRINT*, 1 END SUBROUTINE ADDONE (NUMBER) NUMBER=NUMBER+1 RETURN END

          1 Reply Last reply
          0
          • R raddevus

            Very geeky Foxtrot comic for Fortran celebration! https://i.stack.imgur.com/TKkXL.jpg[^] Sept 20, 1954 the first Fortran program was run. On this day 09/20 – Manning[^]

            T Offline
            T Offline
            theoldfool
            wrote on last edited by
            #18

            At the risk of playing can you top this, IMB 1130, 1965, 8K memory. OOPS: IBM

            >64 If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.

            J 1 Reply Last reply
            0
            • R raddevus

              Very geeky Foxtrot comic for Fortran celebration! https://i.stack.imgur.com/TKkXL.jpg[^] Sept 20, 1954 the first Fortran program was run. On this day 09/20 – Manning[^]

              O Offline
              O Offline
              OldGeezer
              wrote on last edited by
              #19

              If you run this on a CDC 6400 class machine it prints 2 which was both fun and educational :) PROGRAM ONETWO CALL ADDONE(1) PRINT*, 1 END SUBROUTINE ADDONE (NUMBER) NUMBER=NUMBER+1 RETURN END

              1 Reply Last reply
              0
              • T theoldfool

                At the risk of playing can you top this, IMB 1130, 1965, 8K memory. OOPS: IBM

                >64 If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.

                J Offline
                J Offline
                JSilvers
                wrote on last edited by
                #20

                Coded in FORTRAN (before numbered versions) in 1962, IBM 7090. Fortunately graduated to assembler for CDC 3600 by 1964 (for a COBOL compiler)

                Joan F Silverston jsilverston@cox.net nhswinc.com

                1 Reply Last reply
                0
                • C Chris Nic

                  Fortran IV IBM 360 Watfor compiler - February 1971 University of Witwatersrand, Johannesburg as a student. First paid program on same computer as a research assistant December 1971. 50 years ago.

                  G Offline
                  G Offline
                  Gary R Wheeler
                  wrote on last edited by
                  #21

                  My first programming class in college (fall of 1979) used WATFIV on an IBM 370.

                  Software Zen: delete this;

                  1 Reply Last reply
                  0
                  • D dshillito

                    My first program was in Fortran IV and was for an IBM 360 in 1968. Last time I used Fortran was in 1988 on a MicroVax.

                    E Offline
                    E Offline
                    englebart
                    wrote on last edited by
                    #22

                    Good old VMS. We rebooted only when we updated the OS. It would run for years. FORTRAN was the best language for that OS. The C compiler had lots of bugs.

                    1 Reply Last reply
                    0
                    • C Chris Nic

                      Fortran IV IBM 360 Watfor compiler - February 1971 University of Witwatersrand, Johannesburg as a student. First paid program on same computer as a research assistant December 1971. 50 years ago.

                      J Offline
                      J Offline
                      jsc42
                      wrote on last edited by
                      #23

                      FORTRAN IV on WATFOR was my first high level language (if you exclude Honeywell Time Sharing Basic). I was still at school in 1974 and borrowed a textbook overnight and read it cover-to-cover. Then upset the teacher it belonged to by writing more complex programs than she could. (Coding sheets sent to the local county council for mispunching onto 80-char punch cards - turn-round time: 2 weeks)

                      C 1 Reply Last reply
                      0
                      • J jsc42

                        FORTRAN IV on WATFOR was my first high level language (if you exclude Honeywell Time Sharing Basic). I was still at school in 1974 and borrowed a textbook overnight and read it cover-to-cover. Then upset the teacher it belonged to by writing more complex programs than she could. (Coding sheets sent to the local county council for mispunching onto 80-char punch cards - turn-round time: 2 weeks)

                        C Offline
                        C Offline
                        Chris Nic
                        wrote on last edited by
                        #24

                        We had 026 and 029 card punches and we had to punch them ourselves. Submit them to the operators and get your printout then next day. If you knew somebody in there, later the same day.

                        1 Reply Last reply
                        0
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes


                        • Login

                        • Don't have an account? Register

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • World
                        • Users
                        • Groups