Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-unix!sri-spam!mordor!lll-tis!ptsfa!ihnp4!cuae2!ltuxa!ttrdc!levy
From: levy@ttrdc.UUCP
Newsgroups: comp.os.vms
Subject: Re: 2 questions: VAX-C RTL calls and VMS .DIR file entries
Message-ID: <1789@ttrdc.UUCP>
Date: Mon, 29-Jun-87 00:54:45 EDT
Article-I.D.: ttrdc.1789
Posted: Mon Jun 29 00:54:45 1987
Date-Received: Tue, 30-Jun-87 03:12:07 EDT
References: <2405@usceast.UUCP> <258@numm.nu>
Organization: AT&T, Skokie, IL
Lines: 25

In article <258@numm.nu>, Sm@numm.nu (Scott Merrilees) writes:
> Below are the directory routines I wrote a couple of months ago when I needed
> a VMS implementation of the BSD opendir, closedir, readdir and rewinddir
> routines.  The opendir() routine accepts a directory specification and prepares
> the directory to be read, readdir() reads the next entry, etc.  The routines
> are encapsulated in a DCL archive below.
...

Thanks, Scott, for these handy routines.

However, I would like to know if it would be too much to ask of DCL "shar"
posters that they try to keep backward compatibility with the previous few
versions of VMS.  VMS 4.X has been around long enough that long file names
are probably OK, but not everyone has GOSUB yet.  (Is that VMS 4.4 or 4.6?
We're at 4.3 and can't update yet because of applications that won't work
right under later versions of VMS.  UNIX systems often do better at binary
backward compatibility.  This is not a flame, just an [admittedly biased :-)]
observation.)

Thanks for making VMS code easier to unshar in the future....
-- 
|------------dan levy------------|  Path: ..!{akgua,homxb,ihnp4,ltuxa,mvuxa,
|         an engihacker @        |		vax135}!ttrdc!ttrda!levy
|    at&t data systems division  |  Disclaimer:  try datclaimer.
|--------skokie, illinois--------|