Path: utzoo!attcan!uunet!mcsun!ukc!tcdcs!csvax1.cs.tcd.ie!swift.cs.tcd.ie!vax1.tcd.ie!ekelly
From: ekelly@vax1.tcd.ie (EAMON EXT.1795, ROOM 12, 204 PEARSE ST.)
Newsgroups: comp.lang.c++
Subject: Re: Glockenspiel C++ and Commonview?
Message-ID: <4678@vax1.tcd.ie>
Date: 11 Jan 90 08:50:12 GMT
References: <653@telesoft.com> <1990Jan7.202725.14322@sjsumcs.sjsu.edu> <6696@columbia.edu>
Organization: Computer Laboratory, Trinity College Dublin
Lines: 31

In article <6696@columbia.edu>, kearns@read.columbia.edu (Steve Kearns) writes:
> I have been using the extended memory (16M) version of Glock C++;
> it is very nice.  I have never run out of memory, and I can even
> use inline functions, big header files, large code files!  What a luxury! :-}
> 
> -steve
I am also using the extended memory version but I am constantly running out of
memory while compiling and having to split up my code files.
This usually happens at around the 500 line mark with both windows.h and
commonvu.hxx included and a lot of the "#define NOxxxxx" lines deleted.

One of the most annoying features of the C++ preprocessor, I find, is the way it
arranges the names of constructors to make them unique but ignores the 32
character name limit of MicroSoft C. Frequently the 'unique' names produced
byt C++ are not unique to C when truncated to this 32 character limit.

Hopefully version 1.1 of the compiler will fix this (due out next month, they
say.)

Eamon Kelly
Dept of Computer Science
Trinity College Dublin
Ireland

and

Cylon Controls Ltd.
Unit 8, 
I.D.A. Enterprise Centre,
East Wall Road,
Dublin 3