(Dave Day) writes:
>Guy Smith ([log in to unmask]) wrote:
>: 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.
>
>: 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.
>
>I will strongly second that.  I have the same problem with my occasional
>UNIX scripts.  90% of the command files I write (MPE or UNIX) are
>quick and dirty, emphasis on quick.  Hop in the editor, type out
>a couple of lines, and let the system do the typing.  I _don't_ want
>to fool around with file codes, chmods, etc.
>
[nifty UNIX trick chopped]
 
I run into a similar problem with MPEX -- files with a code of 171 (our own
arbitrarily selected code) indicates that what is contained within is an
EXPRESSION program and not an "ordinary command file".  As a result, I'm
constantly getting an error message indicating either that "VAR" is not a valid
command (in the case of forgetting a 171 code) or that whatever is in the first
line isn't valid syntax and the expression programm cannot be compiled.
 
Larry's point is that the specific filecode is only NEEDED if the file is
BINARY.  presumably, most of the time files are stored as ASCII, so this will
be
transparent to most users.
 
In the case of forgetting to chmod a UNIX script, the "dementia" occurs because
there is little or no indication from the error presented that this was
overlooked.  [HINT: MAKE sure the error message chosen for this points people
in
the right direction!]
 
In DOS, you are required to supply the extension of .BAT to indicate the text
contained within is JCL for the OS, but under OS/2, files with .BAT can also be
REXX scripts.  OS/2 and REXX get around this confusion (or add to it) by
requiring the first line of the file to be a C-style /* comment */.
 
Actually, after reviewing this, I realized something that I (as an MPEX user)
quite overlooked: it is difficult to (1) CHANGE filecodes WITHOUT the use of
MPEX, or (2) specify the filecode in EDIT/3000.  [of course, QEDIT lets you do
this easily as well]  Only if the file has the proper code to begin with will
EDIT/3000 work.  So I would chalk this up as a big minus for the filecode idea
for those users who haven't purchased enhanced tools.
 
Tom Emerson
VESOFT technical support