| Title: | DOCUMENT T1.0 |
| Notice: | **New notesfile (DOCUMENT.NOTE) now available (see note 897)** |
| Moderator: | CLOSET::ADLER |
| Created: | Mon Feb 09 1987 |
| Last Modified: | Thu Oct 31 1991 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 897 |
| Total number of notes: | 4397 |
I would like to be able to specify more than one file spec to the /SYMBOLS
and /INCLUDE qualifiers. This would make the DOCUMENT command
qualifiers consistent with other DCL command qualifiers and I wouldn't
have to <INCLUDE> symbol definition files within symbol definitions
files. Then, I would be able to define to various symbols for the
DOCUMENT command depending on the symbol files and included files
my book uses.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 235.1 | next time around | VAXUUM::KOHLBRENNER | Fri Apr 10 1987 08:20 | 2 | |
Duly noted by adding a WISHLIST keyword. Thanks, Mason.
| |||||
| 235.2 | Include symbols? | JAWS::STRYKER | Stew Stryker | Fri Apr 10 1987 12:19 | 2 |
Related question... Can I include the symbols file, rather than
having to remember to specify it on the command line?
| |||||
| 235.3 | Please use /SYMBOLS! | VAXUUM::KOHLBRENNER | Fri Apr 10 1987 12:59 | 17 | |
If you put the <include> in certain places it will be diagnosed
as an error.
If you put the <include> in other places, it will not be diagnosed
as an error in that run, but in some future run you will either
lose the symbols from the CRf or they will be diagnosed as being
duplicates.
If you put the <include> in other places it will always work.
Trying to tell you where you can put it with assurance that it
will work is too difficult.
ADVICE: Use the /SYMBOLS qualifier to include any
file that contains <define_symbol> or
<define_book_name> tags.
| |||||
| 235.4 | Read Note #78.0 | DECWET::CUSTER | Fri Apr 10 1987 13:29 | 4 | |
RE .-1
More ADVICE: Don't use /SYMBOLS to include anything until you've
read Note #78.0.
| |||||