Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ames!sdcsvax!ucsdhub!jack!man!crash!adamsd
From: adamsd@crash.CTS.COM (Adams Douglas)
Newsgroups: comp.sys.amiga
Subject: Re: Manx C
Message-ID: <1490@crash.CTS.COM>
Date: Wed, 31-Dec-69 18:59:59 EDT
Article-I.D.: crash.1490
Posted: Wed Dec 31 18:59:59 1969
Date-Received: Sun, 9-Aug-87 05:34:55 EDT
References: <4540@jade.BERKELEY.EDU> <1836@vax135.UUCP> <4595@jade.BERKELEY.EDU> <3199@zen.berkeley.edu> <17827@amdcad.AMD.COM> <3211@zen.berkeley.edu>
Reply-To: adamsd@crash.CTS.COM (Adams Douglas)
Distribution: comp
Organization: Deep Space Network--JPL/NASA
Lines: 24
Keywords: look at the assembly.
Summary: Why even use int?

I'm not trying to contribute to this back-and-forth which is starting
up, but I personally question the need for using the 'int' type under
Manx. I'm writing a heavily mathematecal application (Planetarium) and
I do not have a single instance of 'int' as a type token anywhere in
my code. Everything is explicitly 'long' or 'short'.

I decided to do this when I read about what Manx does with int's
passed to functions. And I got bit by it with my first piece of test
code, which used 'int'. I also now compile with +L set.

Also, I think 'long' and 'short' keeps you more aware of your memory
usage.


-- 
=======================================================
Adams Douglas	ARPA:crash!adamsd@nosc.mil  AT&T:818-354-3076 <work>
DSN/JPL/NASA	UUCP:{cbosgd | hplabs!hp-sdd | sdcsvax | nosc}!crash!adamsd
		Internet: adamsd@crash.CTS.COM

My opinions! Do you hear? MINE! Not JPL's.

"Do not be angry with me if I tell you the truth." -- Socrates
"Tell the Truth and run."--Yugoslav proverb