Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!sdd.hp.com!spool.mu.edu!uunet!mcsun!hp4nl!nikhefh!x51
From: x51@nikhefh.nikhef.nl (Excursiecommissie)
Newsgroups: comp.sys.acorn
Subject: Re: C versus ARM take 2
Message-ID: <1159@nikhefh.nikhef.nl>
Date: 27 Feb 91 17:50:13 GMT
References: <807@utrcu1.UUCP>
Sender: x51@nikhef.nl (Excursiecommissie)
Reply-To: x51@nikhefh.nikhef.nl (Excursiecommissie)
Organization: Nikhef-H, Amsterdam (the Netherlands).
Lines: 22

In article <807@utrcu1.UUCP> kortink@utrcu1.UUCP (Kortink John) writes:
>
>>You should also bear in mind that the productivity of C programmers (in
>>terms of working object code produced) is about ten times that of assembly
>>language programmers.
>
>True, that is one of the true virtues of *any* high level programming
>language. But that is beside the point. We were discussing speed/size issues.
>
>John Kortink

It is a well known fact that a good algorithm in a compiled language can
be much faster than a bad algorithm, written in assembly.
Now, about the speed issue: If the programmer is using C, he can
implement much faster and has time to spare to think of a better algorithm.
The assembly man is using so much of his time-resources, that he might not
have the time left to think of a better algorithm (Although this is ofcourse
different for the elegant ARM code).

Conclusions: Think before you type. :-)

Axel