[U2] Strange CASE Statement behavior

2011-08-05 Thread John Thompson
I'm running on Universe 10.3.4 on AIX 5.3 on a PICK flavor account. I ran into some really weird behavior with a CASE statement this morning, or at least what I deem to be strange. I won't post the entire program... yet Basically I have some boolean variables that get set earlier in the

Re: [U2] Strange CASE Statement behavior

2011-08-05 Thread John Thompson
To: U2 Users List Subject: [U2] Strange CASE Statement behavior I'm running on Universe 10.3.4 on AIX 5.3 on a PICK flavor account. I ran into some really weird behavior with a CASE statement this morning, or at least what I deem to be strange. I won't post the entire program... yet

Re: [U2] Strange CASE Statement behavior

2011-08-05 Thread Glenn Sallis
Hi John Based on the values of your variables, your CASE construct is behaving perfectly! As far as I can tell, the reason partial_names_found never executes is because the preceding clause in your CASE statement evaluates to /true/. In a CASE block, each clause is checked until a clause is

Re: [U2] Strange CASE Statement behavior

2011-08-05 Thread Marc Harbeson
This is the reason you always place CASE 1 at the end... :-) -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Glenn Sallis Sent: Friday, August 05, 2011 11:00 AM To: U2 Users List Subject: Re: [U2] Strange CASE

Re: [U2] Strange CASE Statement behavior

2011-08-05 Thread John Thompson
...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Glenn Sallis Sent: Friday, August 05, 2011 11:00 AM To: U2 Users List Subject: Re: [U2] Strange CASE Statement behavior Hi John Based on the values of your variables, your CASE construct is behaving perfectly