Xref: utzoo comp.unix.programmer:52 gnu.gcc:1980
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!bionet!snorkelwacker!usc!samsung!uunet!rayssd!sud509!heiser@tdw201.ed.ray.com
From: heiser@tdw201.ed.ray.com
Newsgroups: comp.unix.programmer,gnu.gcc
Subject: ANSI C
Message-ID: <2465@sud509.ed.ray.com>
Date: 18 Sep 90 12:04:56 GMT
Sender: heiser@sud509.ed.ray.com (Bill Heiser - Unix Sys Admin @ Raytheon Company, Sudbury MA)
Distribution: usa
Lines: 33

I'm taking a C course at Boston University -- we're supposed to be writing
in ANSI C.  I've run across a problem in getting so-called ANSI C things
to work (compile) across different architectures (I want to use my unix
machine at home (sysvr3, GCC) to do the development, then just compile
them at school on their machine (the T/A wants to be able to compile the
pgms there).  For example, I just ran into the following anomoly.  

The C books say to use "function prototypes" like this:

void functname(char arrayname[]);

This works fine when I compile it with GCC, and it also works on a
Harris GCX system running Sysvr3.  On the "Sequent" at school, though,
that function causes the compile to die a miserable death.

Should I be doing this some other way to make it work properly?  Anyone
here know anything about the ANSI compatibility of Sequents vs
Harris and/or GCC?  (It MUST be Ansi compatible, since they told us to
write ANSI code ... hmmm...)

Thanks in advance for your ideas on this.

Bill 



-- 
Work:    heiser@tdw201.ed.ray.com
	 {decuac,necntc,uunet}!rayssd!tdw201!heiser
Home(1): bill%unixland.uucp@world.std.com -or- uunet!world!unixland!bill
	 Public Access Unix Coming Soon!
Home(2): Bill.Heiser@f240.n322.z1.fidonet.org (BBS: 1-508-655-3848)
Other:	 heiser@world.std.com     (Pub. Access Unix)