Technology and Trends
 USENET Archives
  
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site scirtp.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!
mcnc!rti-sel!scirtp!dfh
From: dfh@scirtp.UUCP (David F. Hinnant)
Newsgroups: net.lang.c
Subject: Altos C compiler funnies
Message-ID: <557@scirtp.UUCP>
Date: Tue, 10-Dec-85 09:50:26 EST
Article-I.D.: scirtp.557
Posted: Tue Dec 10 09:50:26 1985
Date-Received: Thu, 12-Dec-85 05:21:38 EST
Distribution: net
Organization: SCI Systems, Research Triangle Park, NC
Lines: 21

We have an Altos 586 running Xenix 3.0.  To us, the C compiler has some
rather unusual restrictions.  Specificly, the following declarations are
NOT allowed:
	
	long i; 		MUST be declared as "long int"
	short int i;		MUST be declared as "short"
	unsigned long i;	doesn't work at all
	unsigned long int i;	ditto


However both "unsigned i;" and "unsigned int i;" work OK.  The compiler
error message from "short i;" is "Type clash" while the error message from
"long i;", "unsigned long i", etc. is "misplaced long".

Is this normal for Xenix C compilers, or is just the Altos funny?


-- 
				David Hinnant
				SCI Systems, Inc.
				...{decvax, akgua}!mcnc!rti-sel!scirtp!dfh