Path: utzoo!utgpu!water!watmath!clyde!burl!codas!ateng!chip
From: chip@ateng.UUCP (Chip Salzenberg)
Newsgroups: comp.lang.c++
Subject: Re: c++ for vms
Message-ID: <185@ateng.UUCP>
Date: 11 Feb 88 18:06:44 GMT
References: <303@nih-csl.UUCP> <4800013@uiucdcsm> <6079@tut.cis.ohio-state.edu>
Reply-To: chip@ateng.UUCP (Chip Salzenberg)
Organization: A T Engineering, Tampa, FL
Lines: 18

In article <6079@tut.cis.ohio-state.edu> thomas@tut.cis.ohio-state.edu (Steven Thomas) writes:
>
>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.  ...

Well, it's not available for VMS; but Guidelines C++ for MS-DOS does _not_
patch the executable.  It does some magic with normal C identifiers and
manages to execute all global constructors with only one link pass and no
patching.

So it's possible to avoid post-linking; but I don't know how they do it.

-- 
Chip Salzenberg                 UUCP: "{codas,uunet}!ateng!chip"
A T Engineering                 My employer's opinions are a trade secret.
       "Anything that works is better than anything that doesn't."