🚀 go-pugleaf

I have unpacked the "Harmonics" benchmark program from the net, and
was rather upset about what was left of my favourite language, "C".

(Readers not prepared for flames, please skip to "Comments", below.)

----------
> #Options D=300

What's this?  can't we just pass the options to the C compiler any more?

----------
> // To make it fit 128K Mac

Is this a new form of comment?  Even if the compiler allows it, don't
you ever dare use it.  Even if you can't restrain yourself totally,
DON'T USE IT IN PROGRAMS YOU ARE POSTING TO THE NET!
(Hint, hint, as Chuqui would add.)

----------
> extended seconds;

Huh?  Is this a recent extension to ANSI C that I have missed?

----------
> int fd = open(outfile, 1);
> fprintf(fd, "Calculating the sum of 10,000 terms of the harmonic series\n");

Er, umm, I thought that files to be used with fprintf c.s. should be opened
with *fopen*, not with *open*.  On some systems (including that obscure
system whose name starts with U, ends with an x and has nothing but footnotes
in between) this makes a lot of differences, ya know.

----------
And now for the worst offense to C's syntax:

> printf("Calculating the sum of 10,000 terms of the harmonic series\n");
> /* Lots of printf's */
> register int i;
> register float j = 0;

I am sure that when I last looked, declarations should strictly *precede*
statements.

----------
>     printf("\nThis is a Macintosh with Consulair Mac C 2.0,\n");

WRONG.  This Macintosh (i.e., mine) is running SUMacC.
----------
(End flame)
==========

Comments

I won't comment on programming style, but I think that a program that is
meant as a benchmark could at least have the decency to use only portable
features of a language.  Where this is not possible (e.g., when the timing
difference for using 'extended' numbers is exercised), #ifdefs should
enclose the non-portable sections, and appropriate warnings made in comments.

Alternatively, it is possible that this was one of the first C programs
ever written by its author.  In this case, considering the burden already
placed on the net by inappropriate or duplicate postings, it would have
been better not to post it at all.  Consider this article as a short
lesson in portability.

Admittedly, it is quite possible that the manufacturers of Consulair C
have done their best to hide the fact that there are other versions of
C than theirs, and not provided any clues to the differences.  The fact
that they added #Options, one-line comments and the 'extended' data type
makes one expect the worst.  One suspects that they have never been exposed
to a real C compiler (I mean one running under U**x).  How come they're
such a big success?

BTW, SUMacC floating point (at least what you get when you use 'double' or
'float' variables) is not SANE, and it has some peculiarities, but the
timing was about 22 seconds, independent of whether float or double was
used.  The answer seemed right, at least for 'double'.  (Just to prove
that I *did* manage to correct all the bugs mentioned above.)

	Guido van Rossum, CWI, Amsterdam
	guido@mcvax.UUCP

(Remember, there is more to the Mac than raw computing power.)