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:
"Tony B. Shepherd" <[log in to unmask]>
Reply To:
Tony B. Shepherd
Date:
Thu, 5 Jan 1995 16:28:56 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
On Thu, 5 Jan 1995 09:27:48 -0500, Guy Smith <[log in to unmask]> wrote:
> Subject:      Re: Binary command files?
  {chop}
> 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.
  {chop}
 
Me too.  BTW does EDITOR/QUAD support file codes on ASCII or Binary files
(if I edit one is code still there)?  And what about nuts like me that
build temp files with commands and then XEQ them?
 
Sorry - a well-intentioned idea.  This should have been addressed in 1978 -
that's when UDC support was released (MPE III as I recall).
 
Have you considered a 'compiler' for them - input is UDC or script file,
output is (at least tokenized) binary file?  Sorta like going from the
Basic interpreter to the Basic compiler.
 
Just a thought  --  regards  --  Tony B. Shepherd  --  [log in to unmask]

ATOM RSS1 RSS2