Path: utzoo!mnetor!uunet!husc6!hao!ames!ptsfa!ihnp4!cbosgd!osu-cis!tut!thomas
From: thomas@tut.cis.ohio-state.edu (Steven Thomas)
Newsgroups: comp.lang.c++
Subject: c++ for vms
Message-ID: <6079@tut.cis.ohio-state.edu>
Date: 5 Feb 88 15:55:03 GMT
References: <303@nih-csl.UUCP> <4800013@uiucdcsm>
Organization: The Ohio State University Dept of Computer and Information Science
Lines: 24
Summary: where can I get it?


We recently (last week) purchased c++ for our vms system from Oasys in
Cambridge, MA.  In our initial review we've found that the Oasys system patches
the executable after c++ preprocessor, the c compiler and the linker have all
run.  We called them and asked why it was necessary to patch the executable,
and they stated that the implementation of constructors and destructors require
this patch.  We still remain unconvinced.  So several questions arise ...

1)  Can anyone explain why the executable image should need to be patched after
	creation by the linker?

2)  Can anyone tell us in general about Oasys?  What we've seen so far is this
	patch nonsense and talked with some rather rude support people.  Is
	this company usually rude, quick, cheap and dirty or is this just the
	impression we've gotten?

3)  Are there other versions of c++ available for vms that we should look at?
	(we can return Oasys's stuff within 30 days)  If anyone else is using
	c++ on vms could you tell us what you're using and your impressions of
	it.

Thanks in advance,

Steve Thomas
thomas@osu-cis