Re: "M" apparently a special word in Outline -- WDSCI-L

Vern,

You hit it!

Reverse engineering does work!

It seems that the m, having found occurrences in the lowest branch of the tree, stops looking for other occurrences. Since if found the occurrence in the lowest branch, it shows what it found. That's correct for l, but not for m.
Whereas l just shows the occurrence of l in the word Decimal and stops there on that branch. It knows there are lower tree branches, but doesn't show them, yet gives the ability to dig down in the variable for the occurrence in the source to find all the lines where it's used.

Does that make sense and lead to the cause of the missing lines for m?

I didn't see it before until I was testing what you experienced.

Duane

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Thursday, November 12, 2015 12:21 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] "M" apparently a special word in Outline

Hi Duane

Maybe we each send Edmund a picture of a Canadian 5-dollar bill!

I think that many of us assumed that the outline filter was different from what it is - like if you specify "m" then you'll get entries in the outline that have that letter - such as the word "Decimal". Now I don't know the rules in the code - I am pretty sure a lot of the outline is based, at least once upon a time, on the cross-reference of the compile
- hence the (M) stuff for places where a variable is modified. And it seems that if an entry is selected in the filter, that entries within it are available.

But that behavior wasn't consistent in my cursory testing today. At least to my understanding. Like if my assumptions are close, the "m" in "Packed Decimal" should give the same thing as using the "l" - both letters are in the 2nd word.But it doesn't.

Don't you love trying to reverse-engineer stuff? I'm wrong so often doing it, that I should stop, eh?

Regards
Vern

On 11/12/2015 10:42 AM, Duane Scott wrote:

Hi Vern,

Can't agree more about Edmund and the team. (where do we mail the
$5?)

Well, if one cannot depend on specifics in searches for specific codes, one tends to shy away from them. A search for a variable such as a single letter (in SEU or in LPEX) is daunting. One has to be creative and thoughtful in coding to make it a tad easier, such as adding a viable character like '@m' or character combos that are rare to use in normal keywords. That's been a given for RPG and other languages. And the addition of using SQL and it's available wild cards makes interesting challenges too. While it may be good to use some characters for identification, sometimes it can bite you.

I've forgotten all the work arounds for RPG that I built up over the years to assist in SEU. 20 plus years of use makes it more of instinct than remembering to avoid usages.

Duane

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of
Vernon Hamberg
Sent: Thursday, November 12, 2015 9:44 AM
To: Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] "M" apparently a special word in Outline

Hi Duane

Edmund and the rest of his team are going beyond the basics - the fact
that they regularly participate in this list is a great benefit for us
all. ($5 bill coming in the mail, Edmund!)

I want to comment on one line in your post - see it below here - I'm surprised to hear that you feel you have to modify RPG to get around things an editor forces on us.

I would think no editor should ever have behavior that prevents using what is otherwise valid code. And I am sure the RDi team feels the same way.

Of course, there might be changes in RPG - the editor might be blamed when its the language that changed out from under us. So sometimes the question might be, does the editor hang up? Or does the compile fail?
Those are errors in 2 different places.

Now the LPEX editor is a relatively young thing, compared to SEU - at about 35 years old, SEU is a gray-hair!

So I guess I can say with no fear of contradiction, to everyone, keep reporting issues, and this team will do all they can to deliver remedies.

Cheers
Vern

On 11/12/2015 8:01 AM, Duane Scott wrote:
-snip-

I've not yet learned how to modify RPG code to get around some of the restrictions that are part of using RDi.

-snip-
--
This is the Rational Developer for IBM i / Websphere Development
Studio Client for System i & iSeries (WDSCI-L) mailing list To post a
message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/wdsci-l.

________________________________
________________________________
CONFIDENTIALITY NOTICE: This electronic message transmission is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. If you have received this transmission, but are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this information is strictly prohibited. If you have received this e-mail in error, please contact NALC Health Benefit Plan at 703-729-4677 and delete and destroy the original message and all copies.

--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.

________________________________
________________________________
CONFIDENTIALITY NOTICE: This electronic message transmission is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. If you have received this transmission, but are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this information is strictly prohibited. If you have received this e-mail in error, please contact NALC Health Benefit Plan at 703-729-4677 and delete and destroy the original message and all copies.