Re: CFO: Why C?
From: Richard Heathfield (dontmail_at_address.co.uk.invalid)
Date: 09/06/03
- Next message: Matt: "Re: Huge memory"
- Previous message: Matt: "Re: Huge memory"
- In reply to: VBDis: "Re: CFO: Why C?"
- Next in thread: VBDis: "Re: CFO: Why C?"
- Reply: VBDis: "Re: CFO: Why C?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 6 Sep 2003 05:28:39 +0000 (UTC)
VBDis wrote:
<snip>
> You forgot to mention the machine, for which C was invented. Intel
> processors typically have an architecture and instruction set which is
> absolutely /not/ appropriate for C code. On the proper C machines the ++
> and -- operators are part of the addressing modes, whereas on x86 machines
> the compiler must add explicit instructions for these operators.
As with most of what you say about C, this is wrong. But this is such a
common myth that I think it deserves a specific debunking.
Dennis Ritchie describes reality thusly: "Thompson went a step further by
inventing the ++ and -- operators, which increment or decrement; their
prefix or postfix position determines whether the alteration occurs before
or after noting the value of the operand. They were not in the earliest
versions of B, but appeared along the way. People often guess that they
were created to use the auto-increment and auto-decrement address modes
provided by the DEC PDP-11 on which C and Unix first became popular. This
is historically impossible, since there was no PDP-11 when B was
developed."
-- Richard Heathfield : binary@eton.powernet.co.uk "Usenet is a strange place." - Dennis M Ritchie, 29 July 1999. C FAQ: http://www.eskimo.com/~scs/C-faq/top.html K&R answers, C books, etc: http://users.powernet.co.uk/eton
- Next message: Matt: "Re: Huge memory"
- Previous message: Matt: "Re: Huge memory"
- In reply to: VBDis: "Re: CFO: Why C?"
- Next in thread: VBDis: "Re: CFO: Why C?"
- Reply: VBDis: "Re: CFO: Why C?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|