Strange line that did not report a syntax error

[GCC Consulting]

-----Original Message-----
From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
[mailto:filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com] On
Behalf Of Nancy Palmquist
Sent: Friday, December 30, 2011 3:37 PM
To: filePro Mailing List
Subject: Strange line that did not report a syntax error

Guys,
BTW: Windows 5.0 version of filePro

I was working on a process table and noted the following line - that should
have thrown an error:

lookup zzz=otherfile k=1 i=a -nx    - this lookup did not fail but found 
a successful record - just so you do not think that is what is broken.  
I think this was a browse lookup but I shortened it for our purposes.

lookup xxx=myfile r=(zzz(@rn) -np

Can anyone spot what should have been a syntax error?  Unless I am wrong
about the rules, I think this should be invalid.

Nancy


lookup xxx=myfile r=(zzz(@rn) -np

two mistakes above Missing a closing parenthesis and the open paren should
have been an &

lookup xxx=myfile r=(zzz&@rn) -np  - correct 

lookup xxx=myfile r=(zzz(@rn)) -np - correct as far as the parenthesis go
but still wrong within the parenthesis - see above.


Richard Kreiss
GCC Consulting

Office: 410-653-2813