Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: notesfiles
Path: utzoo!watmath!clyde!burl!ulysses!harpo!decvax!ittvax!dcdwest!sdcsvax!sdcrdcf!hplabs!hp-pcd!hpfcla!hpdcdb!mike
From: mike@hpdcdb.UUCP
Newsgroups: net.lang.c
Subject: Re: Numerical C
Message-ID: <5300001@hpdcdb.UUCP>
Date: Sun, 20-May-84 21:58:00 EDT
Article-I.D.: hpdcdb.5300001
Posted: Sun May 20 21:58:00 1984
Date-Received: Tue, 22-May-84 07:50:57 EDT
References: <1311@mhuxt.UUCP>
Organization: Hewlett-Packard - Cupertino, CA
Lines: 31
Nf-ID: #R:mhuxt:-131100:hpdcdb:5300001:000:1524
Nf-From: hpdcdb!mike    May 18 20:58:00 1984

/***** hpdcdb:net.lang.c / utcsrgv!ray /  9:11 am  Apr 18, 1984*/

	I do practically nothing but numerical computation on the computer.
Although I realize that c was not written to do this, I often use it since
it seems to run faster than F77.  But, I agree with Steve Crandall.  A
complex type would be a real asset since, if I were to implement complex
arithmetic using c as it stands now (I haven't) I would have to write all
sorts of functions to implement + - * / as well as sin, cos, tan, etc. etc.

	It would be fun but I don't want to waste the time debugging all
those routines.  C'mon you compilier hackers, let's have a complex type
(and double complex) in c.  (While you're at it, how about an option to use
the IEEE standard floating point that the VAXEN support.)  It sure would
be nice to have an exponent range of +-300!!

(Shine my shoes, trim my beard, give me service!!  :-)   )

				Ray Allen
				utcsrgv!ray
				(416) 978-5036
/* ---------- */
There are machines on the market that 1) Have complex functions in library
form that are accessible from C or f77 (I know because I've built them). Unfortunately the "complex" type per se isn't available in C but you can easily
hack a struct typedef to make one. Double complex is available too.

Re 2): All HP machines use IEEE floating pt format. Having implemented it
I can attest to the fact that you want to go with IEEE or don't but NEVER
mix the two: No one could figure out the library support for code like that.

				Mike McNelly
				(303) 226-3800