Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!sun-barr!newstop!sun!quintus!jbeard
From: jbeard@quintus.UUCP (Jeff Beard)
Newsgroups: comp.lang.c
Subject: Re: enum implementation
Keywords: enum, types, char/int
Message-ID: <1221@quintus.UUCP>
Date: 26 Jul 89 21:53:09 GMT
References: <396@opusys.UUCP>
Reply-To: jbeard@quintus.UUCP (Jeff Beard)
Organization: Quintus Computer Systems, Inc: Mountain View, Ca
Lines: 12

Having ported several programs using various C compilers, your problem is
NOT enum per se ... but rather attempting to us multiple compilers for the
same appliaction.  I assume that the internal implementation yuou've discovered
is not being used to access and data declared as 'enum'....

C portability ( if one is hanging his hat on the issue) is at the source
level, not the binary *.o level.  Thus attempting to bind several *.o from 
different compilers frought with environmental errors.

One may clearly CC and test (assuming sufficient stubs) any code in any 
environment, but the real delivered executable had better be built from the
same CC, using our friend 'make'.