Re: This is cool.

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Not today IMHO...

With RDi, I can easily jump to the definition of OkList.  By having the the
values in the definition, everything is right there.  I don't have to
scroll to the end of the source to find out what they are.

Yes, if in a procedure the variable would be initialized for every call.
But if that's an issue, there's always the STATIC keyword.

Charles

On Mon, Jul 31, 2017 at 12:27 PM, Mark Murphy/STAR BASE Consulting Inc. <
mmurphy@xxxxxxxxxxxxxxx> wrote:

> Yes, but you don't need O specs to use compile time data. If you use the
> initialized data structure, when does that get initialized/reclaimed? I
> guess if you use it in a procedure, that would be each time the procedure
> is called, and goes away when the procedure ends because it is in automatic
> storage. Maybe a slight benefit if the procedure isn't called, not so much
> if it is called multiple times. So I could see arguing against compile time
> data in a service program, but not necessarily in a program. After all,
> isn't:
>
> dcl-s OkList Char(7) Dim(5) Ascend CTData;
>
> If %Lookup(ErrorReturn.MessageId:OkList) > 0;
>
> ...
>
> **CTData OkList
> CPF3C51
> CPF3C52
> CPF3C53
> CPF3C54
> CPF3C55
>
> A little more idiomatic for RPG (easier for an RPG programmer to
> understand at a glance)