Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!necntc!ames!xanth!kent
From: kent@xanth.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: M2Amiga, a new Modula-2 compiler
Message-ID: <3420@xanth.UUCP>
Date: Tue, 17-Nov-87 23:58:29 EST
Article-I.D.: xanth.3420
Posted: Tue Nov 17 23:58:29 1987
Date-Received: Sat, 21-Nov-87 06:56:46 EST
References: <8711142308.AA01690@cory.Berkeley.EDU> <1074@sugar.UUCP>
Reply-To: kent@xanth.UUCP (Kent Paul Dolan)
Organization: Old Dominion University, Norfolk Va.
Lines: 48

[They're talking machine cycles for a procedure call here, folks]

In article <1074@sugar.UUCP> schaub@sugar.UUCP (Markus Schaub) writes:
>In article <8711142308.AA01690@cory.Berkeley.EDU>,
>dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
>> 
>> 	This straight percentage is going to be very low, so optimizing
>> from 140 to 74 isn't going to be noticeable at all.
>> 
>> 				-Matt
>
>Noticeable? I never said you will notice any change, all compilers
>produce fast (very fast :-) code. But there might be a difference for
>REAL computation where FFP and MathIEEDoubbas routines are called. But
>still you're right.  Faster calls don't make faster routine execution.
>Let's speed up the libraries!

Well, yes, lets do, but the rest of the argument is pretty bogus.

The speed of procedure calls, if you are aware of it and care about
speed of your program, changes the STYLE of your programming.

No matter what the language, I find myself, as a fanatic modular
programming devotee, frequently writing procedures containing only ONE
executable line.  Why?  Because it makes the code much more readable
to put a one word name for what I want done in the calling routine,
and hide the grungy details in a separate procedure.  My goal, not
always achieved, is to have the executable code of any procedure fit
on a single, not too busy screen.

In terms of program maintenance, this is a Good Thing.  But, if the
cost of that procedure call is high relative to the amount of code
being executed, I'm suddenly reluctant to Do Things Right.

So improve the libraries all you want, but remember, high procedure
call overhead has negative affects beyond just the extra time spent;
it can actually worsen coding style.  Thus, time spent improving this
area is also very worth while.

Thanks for listening.

Kent, the (impoverished) man from xanth.

"Computer - a mass occupying my desk with an unusual attraction for
money." (me)

"Sometimes I think mine is a black hole, located in the general
vicinity of my checkbook." (Blaine Gardner, in response.)