CompuServe Thread

#C++

4 messages in this thread
#88424From: Alan EngebretsonFeb 3, 1990 5:13 PM
Thanks for responding to my C++ inquiry. I've been reading about it and want to start using it, so V1.2 might be OK. I do have the 5.02 compiler. I have the A1000 with 2.5 MB and 3 floppy drives but no hard drive (sigh). Are these enough resources to host C++? Do you know what the cost of adding C++ to the 5.02 compiler would be? I appreciate your help.
#88440From: Thomas HoladayFeb 3, 1990 6:38 PM
The gent who did the C++ port for Lattice (Tim Holloway) himself works on an A1000 with 1.5MB and three floppies.
#88487From: Dave LoveFeb 3, 1990 10:36 PM
As I recall, C++ cost about $200 for registered users of the Lattice 5.0 compiler, though you might want to check with Mike Roth (76566,1137) to make certain. As for your configuration, I would think you would be alright. C++ comes with its own include files, and a couple of new commands, but if you can run 5.0, there should be no problem. One last thing: be prepared for one heck of a learning curve! There are so many new ideas to OOP that it takes a while to get them all straight (though I figure I'll have them all down in a year or two :). Good luck, enjoy, and let me know if I can answer any more questions for you. – Dave
#88544From: ned konzFeb 4, 1990 11:44 AM
I've got it, and am using it on exactly the same kind of system. It's sufficient, especially with floppy caching and a non-volatile RAM disk. I've been somewhat frustrated with the support for library development, because of the way the Lattice C treats declarations like: int a; These are generated in every module which includes a class definition which uses static members. Unfortunately, the Lattice C looks at that as something equivalent to: int a = 0; causing problems at link time. (under MS-DOS, the former form ends up in a COMMON area, with no problems at link.) You have to do rather involved things to get some kinds of class libraries to work; the most workable way involves compiling the library modules with a special compiler flag which treats these declarations as externs (all of them!), then including ALL the header files in your main module. Ugly, but probably usable. But as far as learning C++, the package (along with, say, Lippman's book and Stroustrop's book) is fine. I'd ignore Weiner and Pinson's book at first.