🚀 go-pugleaf

In article <3936363@zl2tnm.gen.nz>, don@zl2tnm.gen.nz (Don Stokes) writes:
> jeh@cmkrnl.com writes:
>> To be precisely correct, RMS implements record structure within files.  RMS
>> does not implement files.  Files are implemented by the Files-11 XQP, 
>> or (for RSX-compatible volumes) the ODS-1 ACP, or (for tapes) by the 
>> mag tape ACP.  
> 
> While you are correct here, it's not a useful definition (except to internals
> types).  My point is that RMS is sufficiently pervasive under VMS that the
> normal user or applications programmer has no need to make that distinction;

This is true in most cases.  Nevertheless, I must forcefully disagree with this
philosophy. 

I have taught VMS programming and internals for about 3 years full time,
followed by about nine years of occasional teaching.  And in my experience,
early exposure to correct terminology makes it much easier to learn the
concepts behind the terminology later on. 

Correct terminology encourages the formation of correct mental models, with
which the student is better able to answer questions for themselves.  Sloppy
use of terminology leads to incorrect conclusions.  I've seen this again and
again. 

It's true that only a few of those who are learning system services or RMS
calls today will go on to learn internals later.  And if you could just
figure out who they are, you could avoid bothering the rest with these details.
But there is no way to make that prediction. 

Besides, even though the typical user or applications programmer may not *need*
to make the distinction, it takes all of a few minutes to explain it, and it
isn't going to hurt anyone to make the distinction where it isn't necessary. 

We're going to have to agree to disagree here.

	--- Jamie Hanrahan, Kernel Mode Consulting, San Diego CA
drivers, internals, networks, applications, and training for VMS and Windows-NT
uucp 'g' protocol guru and release coordinator, VMSnet (DECUS uucp) W.G., and 
Chair, Programming and Internals Working Group, U.S. DECUS VMS Systems SIG 
Internet:  jeh@cmkrnl.com, hanrahan@eisner.decus.org, or jeh@crash.cts.com
Uucp:  ...{crash,eisner,uunet}!cmkrnl!jeh