Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!decvax!duke!unc!mcnc!idis!mi-cec!dvk
From: dvk@mi-cec.UUCP (Dan Klein)
Newsgroups: net.unix-wizards
Subject: Re: From VMS to UNIX
Message-ID: <171@mi-cec.UUCP>
Date: Mon, 10-Oct-83 11:02:28 EDT
Article-I.D.: mi-cec.171
Posted: Mon Oct 10 11:02:28 1983
Date-Received: Wed, 12-Oct-83 22:27:28 EDT
Lines: 18

Yes, I guess I stand corrected - the Unix primitive is read().  And all
the other calls are just macros on top of them.  The problem I have
encountered is that they are inconsistantly implemented, and well, we
can flame back and forth about this point for weeks.  Both Unix and VMS
have their shortcomings on all counts.

To answer another point, you *can* implement your own command language in
VMS.  Yes, you *initially* have the choice of either DCL or MCR (and in
a little while, VNX), but after that, you can do as you please.  Look at
HCR's Unity or EUNICE.  Someone even did a history/command completion system
for DCL.  The *nice* thing about VMS (or the bad thing, depending on where
you look) is that you start out *on top of* DCL.  This gives you the advantage
of a bailout point, and also gives you the ability to call on the existing
DCL primitives (you don't have to reinvent the wheel).  Both sh and csh have
to implement their own command scanners (from scratch), while EUNICE simply
uses the existing DCL scanner.  There are wins and loses to both.

		-Dan Klein, Mellon Institute, Pittsburgh