| 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 think there is a bug with conditions. Consider the following code: <condition>(sys\gw) These are conditions, sys and gw. <endcondition> <condition>(am) This is condition, am. <endcondition> Processing for condition sys or gw works as expected; the statement "These are conditions sys and gw." is output. Processing for condition am, however, results in the error "Argument 1 to <CONDITION> is not valid", and both statements are output: "These are conditions sys and gw. This is condition am." I tried processing the sys or gw condition first, then the am condition. Then I deleted all but the .sdml file and processed for the am condition first. I thought maybe something that shouldn't be was being left around, causing the problem; but that's not case. Read the release notes, but didn't find anything there. The people experiencing this are working on a hot document; a fast answer would be appreciated. Version BL8. Doctype or destination doesn't affect this. Thanx Rose
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 633.1 | VAXUUM::KOHLBRENNER | Fri Jul 10 1987 14:28 | 13 | ||
You might get into trouble if you had a space in the (am) argument
to the <condition> tag.
I presume you are setting the condition from the command line with
the /CONDITION qualifier. HOWEVER, if you are using <set_condition>
tags and turning things on and off as you go through the document,
then you must be careful to turn all conditions off (\REMOVE argument)
either at the very front of the input or the very back of the input.
Otherwise the conditions that are set at the start of pass 2 will
be different from the conditions set at the start of pass 1.
bill
| |||||
| 633.2 | The code is clean... | COOKIE::JOHNSTON | Fri Jul 10 1987 15:42 | 12 | |
There are no spaces in the argument. There are no set condition tags; only /condition is used. The sample code that I provided in .0 is a test file that exhibits the behavior I described. Please try running it, as I described. Thanx Rose | |||||
| 633.3 | you are right, it doesn't work. | VAXUUM::KOHLBRENNER | Fri Jul 10 1987 16:38 | 21 | |
Well, you are right, Rose. It's a bug, and apparently in
Baselevel 8 only, because it works fine in BL 7 and BL 9.
A <condition> tag with more than one argument does not work,
unless one of the conditions is actually set. Thus,
<condition>(gw\sys)
does not work unless either gw or sys has been set.
A <condition> tag with only one argument does work, which is
why <condition>(am) does not also generate the error message.
I don't see any way around it, other than using BL 7 or the
new BL 9. (You cannot break the <condition>(gw\sys) into
two tags such as <condition>(sw)<condition>(sys) since that
would amount to trying to "nest" them and nesting doesn't work
either -- never did.)
Sorry. bill
| |||||