Path: utzoo!dciem!nrcaer!sce!knuth!craigs
From: craigs@knuth.UUCP (Craig Statchuk)
Newsgroups: comp.lang.eiffel
Subject: Re: Is comp.lang.eiffel archived anywhere?
Message-ID: <6238@knuth.UUCP>
Date: 2 Jun 89 13:20:18 GMT
References: <61839@yale-celray.yale.UUCP> <5834@microsoft.UUCP>
Reply-To: craigs@cognos.UUCP (Craig Statchuk)
Organization: Cognos Inc., Ottawa, Canada
Lines: 29

In article <5834@microsoft.UUCP> michaelw@microsoft.UUCP (Michael Winser)
writes:
>
>As an aside, how well does eiffel co-exist with Microsoft C 5.1?
>
The answer is: NOT VERY WELL.  This isn't very surprising considering
that MS C lives in a world where "int" is 16 bits and Eiffel
likes "int" to be 32 bits.  In general, these differences can be
handled with judicious use of typedefs and C MACROS.  We have successfully
ported *small* classes to MSDOS and OS/2 without too much difficulty.

Unfortunately, MS C does not perform well with *larger* classes (greater
than 50 lines of Eiffel code).  It seems that the C Macros generated by
pass 4 of Eiffel are too much for MS C to handle.  Typically, we get
three errors:

TEST.C(285) fatal error C1056: compiler limit : out of macro expansion space
MAIN.C(1264) fatal error C1002: out of heap space
BIG.C(345) compiler limit : macro expansion too big

We have successfully compiled the same C code on the SUN, VAX and C370.  Only
MS C exhibits these shortcomings and according to their Technical Support
People, no fixes to these problems are planned.

-- 
Craig Statchuk          P.O. Box 9707      UUCP: uunet!mitel!sce!cognos!craigs
Cognos Incorporated     3755 Riverside Dr.
HUMAN: (613) 738-1440   Ottawa, Ontario     "It's what you learn after you
FAX:   (613) 738-0002   CANADA  K1G 3Z4      know it all that counts..."