Xref: utzoo comp.windows.ms:793 comp.lang.c++:4259
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!iuvax!purdue!haven!umd5!jonnyg
From: jonnyg@umd5.umd.edu (Jon Greenblatt)
Newsgroups: comp.windows.ms,comp.lang.c++
Subject: Glockenspiel C++
Message-ID: <5157@umd5.umd.edu>
Date: 3 Aug 89 17:37:09 GMT
Reply-To: jonnyg@umd5.umd.edu (Jon Greenblatt)
Organization: University of Maryland, College Park
Lines: 40


	Has anyone out there had experience with Glockenspiel CommonView C++?
I find C++ to be rather anoying but seeing as it's becomming a standard in
OOPS it has become my next environment. I have not played with it long enough
to get a real good opinion but I do have a few comments.

	My comments:

1: Usage of too many memory handles. I plan to put in a memory allocator
	I wrote for Xlisp to get around this problem.

2: The examples stink and are unreadable!

3: // I think the "//" commenting scheeme is horrible.

4: The windows interface looks too much like MS Windows C coding and
	does not take real advatage of OOPS to hide this.

5: Given that I have already written a superior OOPS windows interface in
	lisp I will probably port the C parts of it and make my own
	windows hierarchies if possible. I am real picky about not having
	my code look like a bunch C calls with studly caps, weird casts,
	and illogical parameters.

6: C++ still uses a rc file to further seperate the code from its meaning,
	once again I must write my own dialog box code like I did for
	Actor.


7: My opinion of C++ has always been "All the power of OOPS with less
	readability/flexability than C."

	There is a product called C_Talk which I have on order. The little
I saw from it in the adds tells me it it much much better than Common View.
Unfortianaly C++ is becoming a standard so we are all stuck with it. C_Talk
is a small talk environment for C and has a browser and more reasonable
classes. I hope to write a C_Talk to C++ translator in order to maintain
my sanity.

						JonnyG.