Xref: utzoo comp.windows.ms:887 comp.lang.c++:4483
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!aplcen!haven!umd5!jonnyg
From: jonnyg@umd5.umd.edu (Jon Greenblatt)
Newsgroups: comp.windows.ms,comp.lang.c++
Subject: Re: C_Talk review and final review if CommonView C++.
Message-ID: <5272@umd5.umd.edu>
Date: 28 Aug 89 17:58:56 GMT
References: <5258@umd5.umd.edu> <10960009@otter.hpl.hp.com>
Reply-To: jonnyg@umd5.umd.edu (Jon Greenblatt)
Organization: University of Maryland, College Park
Lines: 25


	I think I have found out why the CommonView interface to MS Windows
is so limited. The OASYS company sells their own windows class system 
for Glockenspiel C++. They say they support many UNIX systems, DOS, X Windows,
MS Windows, and support a windows library for systems that don't support
windows like Xenix. With a software product this extensive already written
for CommonView it makes sense that Glockenspiel did not put that much effort
into their own.

	Like I said before the Glockenspiel C++ compiler works great. With
the availability of the windows libraries from OASYS I think this is a more
usable environment than what I previously speculated (given my requirements).
I am still waiting for an compiled OOPS with garbage collection. Apparently
there is a product out called Eiffel but it may be a little while before it's
available in the form I need.

	BTW Actor is the fasted interpreted language I have ever used and it
has met all my needs up to now. At this point my apps are getting into the
thousands of lines and I realy something very small and very fast. I would
strongly suggest Actor for any reasonable apps.

	Sorry for the small flame war I started. I learned a lot this last
week from my foolishness and I hope others benifited from my little fit.

						JonnyG.