document #260
Clarify when expressions allow forward references where it is not clear
| Status: | closed | Start date: | 02/24/2015 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 100% |
|
| Category: | - | |||
| Target version: | - | |||
| Document Type: | Proposed Recommendation |
Description
Some property descriptions to not have the clause about 'no forward reference' when they should have.
Is there a limit to how far ahead an outputValueCalc expression can look?
History
Updated by Steve Hanson over 7 years ago
- Status changed from submitted to accepted
- % Done changed from 0 to 100
Add 'no forward reference' clauses to calendarLanguage and choiceDispatchKey property descriptions.
Add 'no forward reference' clause to setVariable description.
State that how far forward an outputValueCalc expression can reference is implementation-defined.
(Can use similar words to section 9.1 which describes look-ahead when speculatively parsing.)
Updated by Steve Hanson over 7 years ago
Erratum 5.20 in DFDL Experience Document 4
Updated by Steve Hanson over 5 years ago
- Status changed from accepted to closed
(Other formats not available in this archive.