Re: Poll of users of live ILE RPG outline view

I understand that, but all you have to do is look for that assignment. Preferably in an Inz(). If it is somewhere else, it is harder, I agree. But, the Outline already knows where every variable is modified, and once again it is a short step to 'with what?', particularly since you are looking for something very specific '%addr(*IN)', or %addr(*INKA), yes we have a lot of programs that use that one here. But, once you start reading into a data structure, *INKA stops working. So... I guess *INKA isn't as important for the overlays.

Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx


-----Barbara Morris <bmorris@xxxxxxxxxx> wrote: -----
To: wdsci-l@xxxxxxxxxxxx
From: Barbara Morris <bmorris@xxxxxxxxxx>
Date: 04/12/2016 05:53PM
Subject: Re: [WDSCI-L] Poll of users of live ILE RPG outline view


On 4/12/2016 2:28 PM, Mark Murphy/STAR BASE Consulting Inc. wrote:

Why not? I can look at that code snippet and determine quite easily that the data structure overlays *IN. The outline uses a parser that is intelligent enough to know that myInds is a data structure based on p, and that p is a pointer. It is a short step to know that p overlays *IN, that's what %addr(*IN) means. Certainly the parser can figure that out. The other way you can have aliasing is through the INDDS keyword on print and display files. That should be even easier for the outline to figure out.

Since the pointer is a variable, it might not always point to *IN. But I
guess if it _ever_ points to *IN, it could be considered an alias for *IN.