Path: utzoo!utgpu!water!watmath!clyde!att!ucbvax!ean.ubc.ca!kenw%noah.arc.CDN
From: kenw%noah.arc.CDN@ean.ubc.ca (Ken Wallewein)
Newsgroups: comp.os.vms
Subject: Re: EDITLIB/LIBEDIT
Message-ID: <2159*kenw@noah.arc.cdn>
Date: 8 Jul 88 17:41:00 GMT
References: <880706070056.276036b5@LBL.Gov>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 21


  Here's another example of short-sighted solutions to a other short-sighted 
solutions.

  Libraries should have been implemented as a special kind of directory or 
device. One _should_ be able to access library files directly with existing 
facilities, such as DIRECTORY, COPY, EDIT, DELETE, etc.  You could used data 
compressed format for archiving, too.

  Certaily, there are limitations; libraries so not support all of the 
functionality of a normal ODS-2 file structure. But they could certainly be 
treated as a subset.

  Although it would be nice it the functionality was incorporated directly 
into VMS, it _could_ be done as a device driver which translated attributes.
I've seen it done - under CPM!

 /kenw
                                                                 A L B E R T A
Ken Wallewein                                                  R E S E A R C H
kenw@noah.arc.cdn                                                C O U N C I L