CompuServe Thread

#Comeau C++

6 messages in this thread
#18362From: Greg Comeau@Comeau CmptgDec 27, 1991 1:49 PM
>I am glad that you answered me, because I did want to get in touch with >you anyway about your C++ package. How can I get info about your Amiga >version? Comeau C++ 2.1b for AmigaDOS costs $250. It comes with the compiler binary, include files, the iostream library, a rexx command line driver, and some other "helper" utilities. Comeau C++ is a translating compiler that generates C as its object code (note that it is not a preprocessor though: it does full syntax, semantic, error, etc checking and analysis, and it just so happens that at code generation time it decides to take its internal tree representations and output them in C instead of native object code) and will accept either SAS/C 5.10a and above or Manx Aztec C 5.0d and above as its backend code generator. If you would like literature (including reviews and quotes from industry recognized names) you can either inform me of your US mail address or fax number. Or if you like call 718-945-0009 or I would be happy to answer any additional questions here. >and are you planning on continuing your support for this platform? Absolutely. A Comeau C++ 3.0 (which includes C++ templates!) is already in beta and will hopefully be out the door in a few days. >I have heard that the Amiga version of C++ has a few bugs and am wondering >if you will be staying with us. As mentioned we are staying. And not just with the compiler either. 1992 will be the year that things like C++ tools, training, libraries, etc will begin to be released by us and people we are in communication with. Re "a few bugs": it is just that, a few. The compiler has been around close to a year now and we have received about 1 or 2 "serious" problems each month. That brings us to about 15 or so of these serious problems. Fortunately, the 15 reports seem to be 2 (two) problems at most. This is not an excuse, but I've yet to work with a compiler that did have 2 serious problems. We are trying to rid them and I believe 3.0 is able to do that.
#18425From: Peter SmithemDec 29, 1991 12:13 PM
So, how do I get an upgrade to 3.0 when it's available? Peter
#18638From: Greg Comeau@Comeau CmptgJan 3, 1992 10:30 AM
>So, how do I get an upgrade to 3.0 when it's available? Hmm, good question: If I'm not mistaken, didn't you win your Comeau C++ directly from us in a CIS give-a-way?
#18728From: Peter SmithemJan 5, 1992 8:52 AM
Yes, I got the copy you gave away when you had the conference on CIS. I've been having a problem with Aztec C (the beta 5.2 version from their BBS) getting confused with some expressions (it seems to get rather confused sometimes when I use the assert macros), but other than that I'm a satisfied "Customer" <grin>… Peter
#18553From: David McCabeDec 31, 1991 11:48 AM
Greg, I would also like to know how portable across platforms your product is. I know you have a package for MS-DOS, are there other platforms you support? I have C compilers for both Amiga and MS-DOS ( SAS/C and Turbo C 2.0). Thanx for the info. David McCabe WHAP!ping from Montreal! :^)
#18639From: Greg Comeau@Comeau CmptgJan 3, 1992 10:30 AM
>I would also like to know how portable across platforms your product is. I >know you have a package for MS-DOS, are there other platforms you support? I >have C compilers for both Amiga and MS-DOS ( SAS/C and Turbo C 2.0). Oh, it's pretty portable: Comeau C++ is the most diversely ported C++ anywhere. Besides MS-DOS and AmigaDOS, it is available for XENIX, all UNIX 386's, AT&T 3B2, AT&T UNIX PC, IBM RS/6000, Data General AOS/VS, Sun 3, Sun SPARCS, etc. Re the backend C compilers: each platforms we port to does have official support and unofficial support. For instance, under AmigaDOS we have official support for SAS and Manx (but not yet DICE). Under MS-DOS we have official support for MSC. Now this does not mean that it won't work with the other compilers, in many cases it will, however at that point we offer no guarantees. I can tell you that for TC, that you will need to obtain a stand-alone preprocessor, and may have some problems with library comptibility (since what we ship is an MSC'd .LIB).