HP3000-L Archives

January 1995, Week 1

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:
Guy Smith <[log in to unmask]>
Reply To:
Guy Smith <[log in to unmask]>
Date:
Thu, 5 Jan 1995 09:27:48 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
Larry Boyd ([log in to unmask]) wrote:
 
> I have an additionally suggestion.  What if HP selected a filecode that
> would define command files?  If the file is ASCII it would still work, and
> if the file is binary, the code could be checked.
>
> The primary reason for the suggestion is that I've always thought that
> command files and UDCs should have filecodes.  It makes it very easy to
> look at files with listf or MPEX and "see" if they are UDCs or command
> files.
 
I wish to respectfully disagree.  Being the type who never remembers to
do a chmod on my UNIX scripts, and who then spends several seconds in
dememtia figuring out why the script won't run, I know I'd make the same
omission with file codes.
 
However, if HP defined a file code strictly for binary command files and
added the appropriate if-logic (i.e., allow any file code for ASCII and
a specific file code for binary), I would not complain.
 
 =======================================================================
Guy Smith                               Voice:   804-527-4000 ext 6664
Circuit City Stores, Inc.               FAX:     804-527-4116
9950 Mayland Drive                      E-Mail:  attmail.com!bronco!guys
Richmond, VA 23233-1464         Private E-Mail:  [log in to unmask]
 
The thoughts expressed herein are mine and do not reflect those of my
employer, or anyone with common sense.

ATOM RSS1 RSS2