Path: utzoo!utgpu!watserv1!mgardi
From: mgardi@watserv1.waterloo.edu (Mutual Life)
Newsgroups: comp.lang.c++
Subject: commonview
Keywords: Commonview,windows
Message-ID: <577@watserv1.waterloo.edu>
Date: 11 Jan 90 17:58:02 GMT
Distribution: comp
Organization: U of Waterloo, Ontario
Lines: 44


 I would be interested in swapping some experiences with other Commonview
people out there. First some background:

We are using CommonView with Windows on a DOS platform. We are developing
on 70's with 6Megs of memory. Using the 16M version has not created any
compiling problems, but it will not compile anything on a machine with
1M or less. You have to use the !O switch to perform all the substeps
separately.

It was mentioned that someone thinks that one can control Name Mangling
fairly well....Can anyone send me some information on this. I have already
run into Naming problems, and the use of the !M4 switch has been discouraged
by the Tech support people at ImageSoft.

Is 32 character names now an ANSI standard? This is what I was told.

Commonview is a neat package, but it should be noted from our experience 
that it is FAR from complete. To do real programming, we have had to deal
with alot of memory managment techniques (because of Windows), and work
arounds to implement some 'easy' windows constructs. 

We would appreciate any discussion that might be available from users re:
Global/Local heap allocation : 256 segment restriction, declaration of
classes as FAR to be able to pass them into other routines.
DLL creation
Subclassing.

One main problem that we feel is important is the class heirarchy itself.
Controls are separate entities than Windows. This creates alot of problems
when you want to deal with controls as they are in MS_WINDOWS...simply
a window type. ACTOR for instance subclasses both windows and controls from
a class WindowObject.

Again, I would appreciate any comments from users either by phone, or
E-Mail.

p.

Peter DeVries
Mutual Life of Canada
c/o mgardi@watdcsu
(519) 888-3523
(416) 972-0594