David Bond's suggestion that the n' attribute be used is trhe right one, as in
|&parmin setb (n'&x eq 0) --value(s) supplied?
is the appropriate one to use. The behavior you noticed is well documented in
the LR, and in that sense it is neither weird nor anomalous.
Consider the macro instruction
| MCGUFFIN GUBBINS=(a,b,(c,Joe))
For it
|&narg seta n'&gubbins --yields 3
|&n1a seta n'&gubbins(1) --yields 1
|&n2a seta n'&gubbins(2) --yields 1
|&n3a seta n'&gubbins(2) --yields 2
|&k3a1 seta k'&gubbins(3,1) --yields 1
|&k3a2 seta k'&gubbins(3,2) --yields 3
etc., etc. With created set symbols it is even possible, and in my view
desirable, to construct the 'identifiers' of these targets dynamically using
the results of earlier queries to specify how many later identifiers are to be
constructed iteratively.
Worth emphasizing again is that this is WAD behavior.
John Gilmore Ashland, MA 01721-1817 USA
_________________________________________________________________
The New Busy is not the old busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3
