Path: utzoo!attcan!uunet!bu.edu!rpi!julius.cs.uiuc.edu!usc!cs.utexas.edu!rutgers!mcdchg!chinet!patrickd
From: patrickd@chinet.chi.il.us (Patrick Deupree)
Newsgroups: comp.windows.ms
Subject: Re: C++ and Windows 3.0 Programming
Message-ID: <1990Sep19.034207.24313@chinet.chi.il.us>
Date: 19 Sep 90 03:42:07 GMT
References: <1990Sep13.212524.25488@efi.com>
Organization: Company name soon to be announced
Lines: 30

In article <1990Sep13.212524.25488@efi.com> chiu@efi.com (Chan Chiu) writes:
>Hi :
>   I understand that Glockenspiel C++ works with 3.0. I like
>   to know your experience using these two together.
>
Based on what I've heard from many people, you might want to investigate
something other than Glockenspiel C++ and Commonview (assuming you were
looking at Commonview also).  From what I've heard, the best combination
at this time would be C++/Views and Zortech C++.  Hopefully, very soon,
I'll be able to use both of these personally.

>   Last question I have is with memory handles. Standard C++ gets
>   a pointer for an object. By using this pointer, program can peek
>   inside the public section of the object. With Windows, I supposely
>   get "handle" instead of pointer. Does that mean that I should avoid
>   having public section at all ??

You know, this is something I hadn't thought about.  However, in Windows
pointers are pointers and you'll most likely have to deal with them
at one time or another.  If you're passing a pointer to a routine
where the memory at that pointer location may be swapped out, you'll want
to lock that memory.

However, I see no reason why you'd need to change what you declare as
public to private.  You should be able to use C++ more or less normally.
-- 
"What's in a name?  That which we call a rose by any other name would smell
 as sweet."             William Shakespeare
Patrick Deupree ->	patrickd@chinet.chi.il.us   (708) 328-3800
(Please note there are both a patrick and a patrickd at this site)