McFly said:
>My programming training has roughly followed this path:
>
>Pascal, assembly, C, C++, Java, C#.
My programming training has roughly followed this path:
Fortran-II, IBM-1620 machine language, IBM-1620 assembly language (SPS), IBM-360 Basic Assembly Language (BAL), COBOL, APL, PL-1, UAL (United Corporation Assembly Language), Fortran-IV, JOVIAL, Intel 8080 assembly language, Z-80 assembly language, Motorola 6800 and 68000 assembly language, CAL (Cray Assembly Language), C, MasPar assembly language (I once taught that language at university), assembly language for the Motorola 68HC11, Java, C++
Obviously I'm showing my age (I used to be pretty good with a key punch machine punching out computer cards and had programs stored on paper tape). The best assembly language that I've ever coded in was CAL (Seymore Cray was a genius). The funnest programming language was SPS for the IBM-1620 (the machine language was base-10 and self modifying). The crappiest language that I ever knew was JOVIAL (a US Air Force boondoggle programming language for writing orbital mechanics software). The cutest language I ever coded in was APL (to bad it's obsolete). The funnest microcomputer assembly language was for the Motorola 68HC11 (it's a shame Motorola doesn't do computer chips anymore). I detest Fortran and all its dialects. I made a deliberate effort to unlearn Fortran and cleanse my mind of it (I'm a better C programmer because of that). I have no love for Java and C++. I'm now a C bigot and loving it.
For obvious reaons I don't want to learn another programming language.
Gary
Space/Science » in reply to Run code run...C code run...PLEASE!
Programming languages that I've known and forgotten
The whole thread (45 posts)
- a comment on the go for shuttle launch
- re: a comment on the go for shuttle launch
- re: a comment on the go for shuttle launch
- my view as posted on msnbc.com
- Could you imagine what the doctors would say if you had a backup heart?
- Intermittent problems are tough to fix
- re: Intermittent problems are tough to fix
- It's like the "array out of bounds" bug in C programming
- which is itself the best argument against C.
- re: It's like the "array out of bounds" bug in C programming
