Example

Next: Example
Up: The Context Specification and NEEDS Field
Previous: The Context Specification and NEEDS Field

Example

ACTION FIRST
   OBEY
      NEEDS PAR1
      NEEDS PAR2
      NEEDS PAR3
   ENDOBEY
   CANCEL
      NEEDS PAR2
   ENDCANCEL
ENDACTION

For historical reasons, NEEDS specifications can have RANGE or IN constraints but these have no effect.

Next: Example
Up: The Context Specification and NEEDS Field
Previous: The Context Specification and NEEDS Field

ADAM Interface Module Reference Manual
Starlink User Note 115
A J Chipperfield, B D Kelly, S L Wright
3 September 2002
E-mail:ussc@star.rl.ac.uk

Copyright © 2002 Council for the Central Laboratory of the Research Councils