Related articles |
---|
Quality of VAX compilers firefly@diku.dk (Peter \Firefly\Lund) (2006-06-03) |
Re: Quality of VAX compilers lkrupp@pssw.nospam.com.invalid (Louis Krupp) (2006-06-05) |
Re: Quality of VAX compilers firefly@diku.dk (Peter \Firefly\Lund) (2006-06-07) |
Re: Quality of VAX compilers jafred@verizon.net (John Fredrickson) (2006-06-07) |
Re: Quality of VAX compilers gah@ugcs.caltech.edu (glen herrmannsfeldt) (2006-06-11) |
Re: Quality of VAX compilers tom@kednos.com (Tom Linden) (2006-06-11) |
Re: Quality of VAX compilers jvorbrueggen@mediasec.de (=?ISO-8859-1?Q?Jan_Vorbr=FCggen?=) (2006-06-12) |
Re: Quality of VAX compilers tom@kednos.com (Tom Linden) (2006-06-15) |
Re: Quality of VAX compilers kenrose@tfb.com (Ken Rose) (2006-06-15) |
Re: Quality of VAX compilers henry@spsystems.net (2006-06-15) |
From: | "John Fredrickson" <jafred@verizon.net> |
Newsgroups: | comp.compilers |
Date: | 7 Jun 2006 23:18:28 -0400 |
Organization: | Compilers Central |
References: | 06-06-009 |
Keywords: | history, architecture |
Posted-Date: | 07 Jun 2006 23:18:28 EDT |
Peter,
I don't know much about the internals of the VAX compilers other than
they were all optimizing compilers that subscribed to the same calling
standard, enforced by the VMS operating system and the one
linker. That's why you could develop multiple modules of a software
system in multiple languages (VAX-BASIC, VAX-FOTRAN, VAX-COBOL, etc)
and link the object modules together into a single EXE file.
The VAX hardware and VMS Operating System were designed together and were a
beautiful system. Digital Equipment Corporation (DEC) did a good job
transitioning to Alpha and OpenVMS.
John Fredrickson
"Peter "Firefly" Lund" <firefly@diku.dk> wrote in message
>I seem to have acquired an acute fascination with the VAX architecture.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.