Comments on: LOOKUP

By: bogeybetsy

bogeybetsy — Thu, 16 Jul 2009 16:38:35 +0000

Hey Sloopy,

I saw your tip about the back loading of arrays. I applied it and I got a program that runs for about an hour down to about 15 minutes. That was an awesome tip! Thanks!

Now…

…In other words it will not change on an unsuccessful LOOKUP. You can use NOT %Found to test for a failure to find correct index.:…

For LOOKUP, the index value becomes 1 if it is unsuccessful. For %LookUp, the index value becomes 0.

Regards,

Alln

By: sloopy

sloopy — Thu, 16 Apr 2009 15:39:01 +0000

I got here before you for a change, Cwc!

By: cwc

cwc — Wed, 15 Apr 2009 14:44:07 +0000

Sorry Sloopy, I didn’t see that you had already elaborated on this.

By: cwc

cwc — Wed, 15 Apr 2009 14:42:33 +0000

With either format, the plus sign to continue a line isn’t needed – but with free format, the compiler does need a semi colon to mark the end of each statement.

By: sloopy

sloopy — Wed, 15 Apr 2009 13:59:12 +0000

You don’t need a plus sign in fixed or free-format RPG to extend code to new lines.

In /free format code, I have noticed that often the code becomes quite untidy and difficult to read – this is not a fault with free-format code, but in the attitude of the writer.

In fixed-column AND in free-format, I tend to align code when it extends to other lines – example below (which will be mucked up by the text editor!)….

       Eval      RtnData = EditFld( wkData        
                                  : dbffldb (I)   
                                  : wkFldType     
                                  : dbffldd (I)   
                                  : dbffldp (I)   
                                  : wkEdtCde      
                                  : '    '      )

Sloopy

By: woodengineer

woodengineer — Tue, 14 Apr 2009 16:16:44 +0000

I agree with CWC – be /free if you can.
If that is not allowed in your shop I believe you can use the + (plus sign) to extend an EVAL statement to a second, third, fourth line as needed.

By: cwc

cwc — Mon, 13 Apr 2009 14:21:09 +0000

To confirm, all BIFs will also work in fixed format via the EVAL operation, although you would likely run into the dreaded column cram with a few of them, depending on the number of parameters and how long your variable names are. So, I’d rather be /Free.

By: woodengineer

woodengineer — Thu, 09 Apr 2009 15:49:07 +0000

If you like built-in functions, try %lookup.
For example, in free form RPG, X = %lookup(searchValue : Array)
X will be zero if searchValue is not found.
I think this also works with an EVAL statement in fixed format RPG.