| 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 |
The following sample definition list produces tag translation messages
with a severity level of W.
<definition_list>
<definition_list_head>(Just Another Heading)
<deflist_item>(Item A)
<deflist_item>(Item B)
<deflist_item>(Item C)
<enddefinition_list>
The message claims that I'm trying to nest <DEFLIST_ITEM> tags.
%TAG-W-NONESTING, at tag <DEFLIST_ITEM> on line 139 in file....
I suppose it expects to see a <DEFLIST_DEF> tag before it encounters another
<DEFLIST_ITEM> tag.
The tag translator doesn't complain when you omit the definition in
PARAMDEFLISTs and QUALDEFLISTs. I was hoping all the definition lists
would behave similarly.
The output is OK, though.
Could this warning be turned off?
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 528.1 | but if there are no definitions... | CLOSET::ANKLAM | Thu Jun 18 1987 23:39 | 6 | |
I don't understand why you have items that have no definitions ?
If there's a bug anywhere, it's in the fact that <qualdeflist>s
and <paramdeflist>s don't signal a warning.
| |||||
| 528.2 | I agree | PANAMA::GILLIAM | Fri Jun 19 1987 11:11 | 12 | |
It's heresy, I know. There are extenuating circumstances.
I would never create a definition item without a definition. However,
I'm extracting (among other stuff) definition
items (the tag and the argument) from parameter, qualifier,
and generic definition lists in other manuals. I don't need the
definition.
If, as you say, QUALDEFLISTs and PARAMDEFLISTs don't adhere to the
rule then, perhaps I should also extract the accompanying
<QUALDEF>, <PARAMDEF>, and <DEFLIST_DEF> tags WITHOUT their arguments
just to make everything perfectly legal.
| |||||