Re: [U2] Universe 10.1 Itype possible parsing problem

2008-01-10 Thread john reid
Mitchell [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 08, 2008 6:14 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Universe 10.1 Itype possible parsing problem I would think that honoring a reasonable order of operations when parsing would resolve this. The extraction operator

RE: [U2] Universe 10.1 Itype possible parsing problem

2008-01-10 Thread Jerry Banker
: Thursday, January 10, 2008 8:10 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Universe 10.1 Itype possible parsing problem Not to prod an already dead one, but the same problems occur using comparisons on outcomes or '@' items. For example: SOME PROCESS; IF @1= 5... yields an incorrect

Re: [U2] Universe 10.1 Itype possible parsing problem

2008-01-09 Thread Herve Balestrieri
This interesting feature is reproduced also at release 9.5.1 of UniVerse (and likely from the beginning), but this one was not yet referenced at IBM nor its predecessors. Note that compiling the DICTionary displays something abnormal that could alert on the problem : CD VOCLIB Compiling

Re: [U2] Universe 10.1 Itype possible parsing problem

2008-01-09 Thread john reid
I appreciate the feedback. Thanks all. john On 1/9/08, Herve Balestrieri [EMAIL PROTECTED] wrote: This interesting feature is reproduced also at release 9.5.1 of UniVerse (and likely from the beginning), but this one was not yet referenced at IBM nor its predecessors. Note that compiling the

RE: [U2] Universe 10.1 Itype possible parsing problem

2008-01-09 Thread Jerry Banker
-Original Message- From: Geoffrey Mitchell [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 08, 2008 6:14 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Universe 10.1 Itype possible parsing problem I would think that honoring a reasonable order of operations when parsing

Re: [U2] Universe 10.1 Itype possible parsing problem

2008-01-08 Thread Colin Jennings
I think it's to do with the compiler seeing the = symbol. I knew there was a reason I always use spaces!! Colin. In the following query, a file is listed with two identical itypes, save for field 2 spacing, as shown below. Fields 3 and 6 are all equal in the query shown. The difference is

RE: [U2] Universe 10.1 Itype possible parsing problem

2008-01-08 Thread Jerry Banker
What it is doing is evaluating as: If @record is less than 3 is greater-than or equal to @record6 then 1 else -1 Or In other words: If 0 is greater-than or equal to 20071217:224240 then 1 else -1 -Original Message- From: john reid [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 08,

RE: [U2] Universe 10.1 Itype possible parsing problem

2008-01-08 Thread Jerry Banker
Subject: RE: [U2] Universe 10.1 Itype possible parsing problem What it is doing is evaluating as: If @record is less than 3 is greater-than or equal to @record6 then 1 else -1 Or In other words: If 0 is greater-than or equal to 20071217:224240 then 1 else -1 -Original Message

Re: [U2] Universe 10.1 Itype possible parsing problem

2008-01-08 Thread Geoffrey Mitchell
. -Original Message- From: Jerry Banker [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 08, 2008 4:46 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Universe 10.1 Itype possible parsing problem What it is doing is evaluating as: If @record is less than 3 is greater-than or equal

RE: [U2] Universe 10.1 Itype possible parsing problem

2008-01-08 Thread Stevenson, Charles
Try DLIST. It's like VLIST, but for I-descriptors. DLIST decompiles the I-descriptor into something that looks an awful lot like the decompiled basic object that VLIST shows. I put 2 I-descriptors called NICELY.SPACED and CRAMMED in DICT VOC compiled them. Look how the 2 decompile into