Path: utzoo!attcan!uunet!lll-winken!ames!apple!mas1!tma
From: tma@mas1.UUCP (Tim Atkins)
Newsgroups: comp.lang.eiffel
Subject: Re: Is comp.lang.eiffel archived anywhere?
Message-ID: <1906@mas1.UUCP>
Date: 9 Jun 89 03:23:05 GMT
References: <61839@yale-celray.yale.UUCP> <5834@microsoft.UUCP> <6238@knuth.UUCP>
Reply-To: tma@mas1.UUCP (Tim Atkins)
Organization: Measurex Automation Systems, Cupertino, CA
Lines: 18

In article <6238@knuth.UUCP> craigs@cognos.UUCP (Craig Statchuk) writes:
>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
...
>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
...

I experienced the same problems with Microsoft C when I ported Objective C to
OS/2.  I ended up porting cpp from PCC to OS/2 to solve the problem.  Of course
this required a bit of hacking to deal with some of Microsoft's conventions.

By the way, does anyone anticipate an OS/2 implementation of Eiffel anytime
soon.  OOPS is a wide open market in this environment.