Path: utzoo!attcan!uunet!nih-csl!nih-csl.dcrt.nih.gov!sandy From: sandy@nih-csl.dcrt.nih.gov (sandy orlow) Newsgroups: comp.lang.c++ Subject: Re: NIHCL and Turbo c++ (again) Message-ID: <530@nih-csl.nih.gov> Date: 24 Sep 90 21:51:40 GMT References: Sender: news@nih-csl.nih.gov Reply-To: sandy@nih-csl.dcrt.nih.gov (sandy orlow) Distribution: comp Lines: 21 I made an effort to port NIHCL to Turbo C++ on a COMPAQ-386 with many mega-bytes of memory. There were many problems -- a few portability problems, a few Turbo compiler bugs, but the upshot of my effort was that Turbo C++ cannot currently compile a large enough module to support the NIH Class Library. Turbo-C++ appears to adhere to a 640K memory limit in its own execution. I went to some lengths to get many of the classes compiled and, Turbo bugs aside, had some success. However, I ended my efforts when I came to the following conclusion: The NIH Class Library is designed for Object-Oriented programming. In my experience, object-oriented programs are large beasts with deep nesting of header files, and modules for classes that are coupled to many other classes can become large. If a compiler has trouble with NIHCL as it is, I suspect its ability to compile useful software built with NIHCL, and useful object-oriented software in general. Sandy Orlow, Systex, Inc. at the Computer Systems Laboratory National Institutes of Health sandy@alw.nih.gov