[comp.lang.c++] NIHCL and Turbo c++

av@kielo.uta.fi (Arto V. Viitanen) (09/24/90)

This has been asked before by somebody else, but since there was not answer
(at least on news), here goes again...

Is there implemetation of NIHCL for Turbo C++ (at least partial) ?
--
Arto V. Viitanen				         email: av@kielo.uta.fi
University Of Tampere,				   	    av@ohdake.cs.uta.fi
Finland

sidney@saturn.ucsc.edu (Sidney Markowitz ) (09/24/90)

In article <AV.90Sep24083928@kielo.uta.fi> av@uta.fi (Arto Viitanen) writes:
>Is there implemetation of NIHCL for Turbo C++ (at least partial) ?

There is no complete port of NIHCL to Turbo C++, and there will not be
using the current version of the compiler -- NIHCL class structure exceeds
some absolute table size limits of the compiler in several places.

I would be interested in hearing of a partial port, however. I know of
one person who is in the process of running NIHCL 3.0 through some awk
and sed scripts for the purpose of changing file names to MSDOS compatible
form. Once that's available, I could post it somewhere to ease the process
of working with it for anyone who is interested.

-- sidney markowitz <sidney@ai.mit.edu>
  [Note: the account sidney@saturn.ucsc.edu is disappearing soon]
  Disclaimer: I work for Borland, but I don't speak for Borland

sandy@nih-csl.dcrt.nih.gov (sandy orlow) (09/25/90)

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

erik@echocen.UUCP (Erik Ch. Ohrnberger) (09/29/90)

In article <AV.90Sep24083928@kielo.uta.fi>, av@kielo.uta.fi (Arto V. Viitanen) writes:
> This has been asked before by somebody else, but since there was not answer
> (at least on news), here goes again...
> 
> Is there implemetation of NIHCL for Turbo C++ (at least partial) ?

I'd be interested in this port also.  I think that studying the code, and
whatching it run in the debugger would be a great learning aid (I'm
currently teaching myself C++ with TC++)

	Thanks,		Erik.