| General > General Technical Chat |
| C language 50th anniversary |
| << < (9/13) > >> |
| DiTBho:
I mean, the *compiler* used on NextSTEP computers was obtained from GNU CC, modified and extended as a compiler for the Objective C language by NeXT Computer, Inc. for use on NextSTEP computers. And they made it 2x-faster than Gcc on HPUX, that's impressing :o :o :o |
| jfiresto:
I started in 1983 with DECUS C, which was written in and generated PDP-11 assembler. It was my introduction in how to trick a compiler to do your bidding, and not excite compiler bugs. :) Although C compilers have improved a lot over the years, I can think of many less pleasant things to do than study PDP-11 assembler. |
| Tomorokoshi:
--- Quote from: BrianHG on July 23, 2022, 07:47:47 am --- --- Quote from: Tomorokoshi on July 22, 2022, 09:59:44 pm --- --- Quote from: BrianHG on July 22, 2022, 09:46:26 pm ---I tried C on my firs Amiga with a 68000 processor, 2.5mb ram and a super slow HD. No way, too long to compile. (1989ish) I tried again when I got my 25MHz 68030 Amiga 3000 with 10mb ram and a top performance 7200 RPM SCSI HD. (1993ish) Ok, now I was hooked as compiling time was actually good. Though a lot of code was copy & paste modified examples from existing source code with my algorithms in-between. I didn't delve deeper into a modern C compiler until I had access to a C compiler for Microchip MCUs and had to do a DSPIC project for my exercise bike controller. Then it was more fun as compile times were only around 2 seconds. --- End quote --- Yes, I had have Lattice C on the Amiga 3000. --- End quote --- I currently have SAS/C version 6.3, still alive and kicking... I think I had Lattice on my A1000, however, I no longer have that computer. Hmmm, I just tried a compile and it took 15 seconds on my A3000. Hmmm, I just tried the same compile on a JIT WinUAE emulated A3000. Half a second to compile the same project. --- End quote --- That's right! It was updated from Lattice to SAS! The machine is currently disassembled. The battery leaked, and I need to repair the damage. |
| langwadt:
--- Quote from: Ed.Kloonk on July 23, 2022, 03:32:14 am --- --- Quote from: langwadt on July 22, 2022, 11:25:46 pm --- --- Quote from: mclute0 on July 22, 2022, 09:34:22 pm ---I will have to dig out my original book, The C Programming language by Brian W. Kernighan & Dennis M. Ritchie and read it all again. True heroes the modern world. Salute! --- End quote --- I have two, the one I bought at uni and the one my dad used at some point. I wonder if there is a way to tell when it was printed --- End quote --- The wiki says --- Quote ---Publication date 1978 (1st Edition) 1988 (2nd Edition) --- End quote --- https://en.wikipedia.org/wiki/The_C_Programming_Language --- End quote --- that's the publishing date, they didn't print all of them at once |
| BrianHG:
--- Quote from: SiliconWizard on July 22, 2022, 10:12:11 pm ---That's funny. I had a Mac Plus at some point with 2.5MB RAM and Think C, and it was perfectly usable. --- End quote --- What was the build time of a complete project with a full GUI libraries in the source code? |
| Navigation |
| Message Index |
| Next page |
| Previous page |