HP3000-L Archives

July 1998, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Leonard Berkowitz <[log in to unmask]>
Reply To:
Leonard Berkowitz <[log in to unmask]>
Date:
Thu, 16 Jul 1998 13:28:06 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (41 lines)
$NEWPASS and $OLDPASS is a temporary file. No, that's not a mistake in
grammar. They are the same file. In the creation of the file $NEWPASS is
used (in my example I was using EDIT/3000; Marshall Medoff mentions its use
in compling --> PREPing/LINKing; I could have used this file in the context
of FCOPY). In the use of the file $OLDPASS is used.

My posting was based on astonishment that $NEWPASS was being kept in the
PERMANENT DOMAIN. That was not even accurate reporting on the part of
EDIT/3000. The resulting $OLDPASS could only be seen by LISTFTEMP, not
LISTF.

Leonard S. Berkowitz







Marshall Medoff <[log in to unmask]> on 07/16/98 10:04:01 AM

Please respond to [log in to unmask]

To:   [log in to unmask]
cc:    (bcc: Leonard Berkowitz/THP)
Subject:  Re[2]: $NEWPASS a permanent file????




Doesn't the system know about $newpass as a permanent file but after
writing to it and closing it, the system automatically renames it
"$oldpass" as in Joe's example print?

Don't the language compilers always write to $newpass, but when you "prep"
you have to prep from $oldpass, unless a user file is specified?

Just a few things from way back in the closet.

MM

ATOM RSS1 RSS2