Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site decwrl.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!harpo!decvax!decwrl!rhea!vaxuum!dyer
From: dyer@vaxuum.DEC (Where's the falafel?)
Newsgroups: net.lang.c
Subject: Re: C Compiler for VAX/VMS Wanted
Message-ID: <6489@decwrl.UUCP>
Date: Sun, 25-Mar-84 23:35:09 EST
Article-I.D.: decwrl.6489
Posted: Sun Mar 25 23:35:09 1984
Date-Received: Mon, 26-Mar-84 21:03:47 EST
Organization: DEC Engineering Network
Lines: 31

| Re: C Compiler for VAX/VMS Wanted |

	Sorry, Nelson, I can't get mail to you...

	I work for DEC up here in Nashua, where VAX/VMS* is made.  We have
another building right next to ours where they make VAX C.  VAX C is the
language I use the most, and it's a good systems/applications language
for the VAX.
	It has UNIX-compatible functions, so most UNIX C programs will
run on it.  If you're going to be spending any time with VMS, dealing
with it on a systems level, you'll probably end up using VMS' I/O instead
of the "standard" C I/O (or more likely, you'll use a combination of the
two).
	Pluses:  You have access to VMS' rich library of functions and
system services; you can write a program in a number of different langu-
ages (i.e., if you have to work on a FORTRASH program, you can replace
it with C); VAX C is supported (and with that you get big-company features
like updates, etc.).
	Minuses:  No seperate pre-processing (it's built into the compiler);
no machine-code output (though you can see it in the listing file); I don't
know how much it costs. 
	VMS also has a utility called MMS that works like MAKE and then
some.  So don't lose those MAKEFILEs!
		<_Jym_>

| Jym Dyer | DEC Documentation Production Software | Nashua, New Hampshire |
	   | ...{allegra|decvax}!decwrl!rhea!vaxuum!dyer |

-------------------------------------------------------------------------------
*VAX/VMS is a trademark of Digital Equipment Corporation, so pipe that in
your shell and smoke it!