HP3000-L Archives

November 1998, 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:
Jeff Vance <[log in to unmask]>
Reply To:
Jeff Vance <[log in to unmask]>
Date:
Wed, 4 Nov 1998 09:53:08 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
On Nov 4, 11:22am, [log in to unmask] wrote:
>      I have a question regarding the :LISTF command...The documentation
>      says that :LISTFILE is a superset of :LISTF, does that
>      mean that :LISTF calls :LISTFILE?

Not directly.  The LISTF command is parsed in compatibility mode (CM)
and follows all CM parsing rules.  It also does not support POSIX syntax
filenames.  LISTFILE is parsed in native mode (NM) and supports POSIX
syntax filenames.  So, all parameter parsing and validating is done
separately; however LISTFILE and LISTF both call the same code to
traverse the diretory, collect the data and perform the output to $STDLIST.
LISTF just supports less features than LISTF.  Besides the filename syntax,
other differences (off the top of my head) are:  LISTFILE supports:
  - ;name=
  - ;seleq=[...]
  - ;tree | notree
  - ;temp and ;permtemp
  - format names rather than just numbers
  - a list of filesets rather than a single fileset
  - some output differences, most noted when the output is redirected to
    a file, or is generated in a job.

>      An unequivocal statement would be appreciated.

Hope that helps,
Jeff Vance, CSY

--

ATOM RSS1 RSS2