Syntax error on array index

John Esak john at valar.com
Fri Jan 22 19:30:57 PST 2010


Ha!... Helping one of the original genius's of filePro is my plearusre, so
thank you!  How often is that going to happen anyway! :-)

John


> -----Original Message-----
> From: filepro-list-bounces+john=valar.com at lists.celestial.com 
> [mailto:filepro-list-bounces+john=valar.com at lists.celestial.co
m] On Behalf Of Barry Wiseman
> Sent: Friday, January 22, 2010 10:25 PM
> To: Filepro_List
> Subject: Re: Syntax error on array index
> 
> Bingo!  Yes, there are L1), L2) etc. associated fields in the 
> map.  (But no J's or K's.)  I vaguely remembered about this 
> bug but couldn't put my finger on it, thanks for jogging my 
> memory, John.
> 
> On 1/22/2010 4:31 PM, John Esak wrote:
> > Looks to me like the same old bug about associated fields 
> and closing
> > parens.  Do they have an L associated field?
> > I think Ken addressed this problem and maybe the fix caused 
> this behavior,
> > or it's the same bug and it wasn't addressed because it 
> would take rewriting
> > the parsor too much.
> >
> > John
> > 	
> >
> >> -----Original Message-----
> >> From: filepro-list-bounces+john=valar.com at lists.celestial.com
> >> [mailto:filepro-list-bounces+john=valar.com at lists.celestial.co
> > m] On Behalf Of Barry Wiseman
> >> Sent: Friday, January 22, 2010 4:08 PM
> >> To: Filepro_List
> >> Subject: Syntax error on array index
> >>
> >> 5.0.15 on linux
> >>
> >> I was asked to debug why rcabe reports the following error
> >> (and then SEGV's when you press Enter):
> >>
> >> *** A filePro Error Has Occurred ***
> >>
> >> Line Number: 1934
> >>
> >> code(g)="F";dscr(h)=""{sj; amt(j)=isa ;ext(k)=isa ;glc(l)=iqi
> >>                                                            ^
> >> Process contains a syntax error at position indicated.
> >>
> >>
> >> glc is an array mapped to a lookup, l is (3,.0), iqi is an
> >> uncast DECLARE. Actually the glc(l) was the problem, even
> >> glc(l)="" gave the same error.
> >>
> >> Long story short, the following change fixes it.
> >>
> >> code(g)="F";dscr(h)=""{sj; amt(j)=isa ;ext(k)=isa ;glc(l )=iqi
> >>                                                         ^^^^
> >>
> >> Is this a known bug in 5.0.15?  Without the space, what does
> >> rcabe think he's seeing?  The tags "glc" and "l" are both
> >> quite unambiguous in the program.  Why don't the similar
> >> "amt(j)" and "ext(k)" throw errors?
> >>
> >>
> >> _______________________________________________
> >> Filepro-list mailing list
> >> Filepro-list at lists.celestial.com
> >> http://mailman.celestial.com/mailman/listinfo/filepro-list
> >>
> >
> >
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
> 



More information about the Filepro-list mailing list