Change requests on searching problems -- CODE400-L

I guess Erich is having the same thoughts I had with the cross reference
problem.  I was going to mention my requests on searching problems tomorrow
but I have decided to report them all now since the subject is fresh.
Developer suggestion on the "View" -> "Cross reference" problem of not
seeing the references to the variable which is already being fixed: Instead
of searching for just a text string, make sure the character before and
after text string compared to is either "a binary operation (like +,=,
<,...)", "(", ")", " ", or ";"(I suppose the ";" would be for free form
people).
For example, if your variable is "X", I would want to see all references to
that variable, not a string or other variables containing "X".  Maybe use
this same search criteria algorithm for the extract field selections
(mentioned later).  In other words, I would want to see lines like
               "C     Eval    X = X + 1"
               "C     Eval    Result = 'The result is: ' + %Trim(%Char(X))"
Not lines like
               " * Get the next subscript (why show this line?)"
               "C     Eval    Text = 'Why show this line? Does the
suggestion make sense?'"

I don't know how this would affect speed though.

The following are change requests on searching problems I would like to
have resolved or reviewed:
Change request #1: In "View" -> "Cross reference", show the line of text
the variable appears on (similar to extract fields list), not the line
number.  I suppose if there is a reason to show line number too then so be
it.  I don't know of any programmers who would keep track or care about the
line number.

Change request #2: Limit field references from Extras -> Fields -> Extract
fields(LIST) then double-click field then right click and select "Field
Selections" by search criteria above.
This becomes important if you have generic names in a display file or
printer file.  I suppose the search criteria mentioned above would not be
as important in this case since the number of unique field names might be
greater than the number of unique variable names.

I am intersted to see how far my 2 cents flies.

Craig Strong


*** Michele Cummings previously wrote ***
Hi Erich,
I understand you now!!  It appears as if the design of this function is not
complete.  I will open an apar for this and try to
fix it in the next service pack if possible.  I'll let you know the apar
number after I open it.

Michele Cummings

WDT iSeries Development
IBM Toronto Lab



"Erich W. Schasse" <Schasse@Wiedemann.de>@midrange.com on 11/08/2001
10:48:42 AM

Please respond to code400-l@midrange.com

Sent by:  code400-l-admin@midrange.com


To:   <code400-l@midrange.com>
cc:
Subject:  AW: Cross Reference Problem


Michele,

thanks for the answer, but I think your answer doesn't met my question.

I'm still not not interested whether the variable is modified or not. That
can I see in in compiler listing.

I want only know, in which line the variable is referenced. I am speaking
about the java-tool what you can find under the menu bar "VIEW" with ethe
item "Cross-Reference" (I hope the back translation is correct: in my
german
version you found it under "Sicht"/"Querverweis").



Erich W. Schasse



-----Ursprungliche Nachricht-----
Von: code400-l-admin@midrange.com
[mailto:code400-l-admin@midrange.com]Im Auftrag von mcumming@ca.ibm.com
Gesendet: Donnerstag, 8. November 2001 16:01
An: code400-l@midrange.com
Betreff: Re: Cross Reference Problem


I'm not sure if I understand you completely but this is what I think you
are asking...

With the statement below, you are expecting VATEST to appear in the
cross-reference as being modified on that line.
EVAL      *IN36 = (VATEST = 24)

VATEST is not modified in the above statement.  It is only compared to 24
and either
'1' will be assigned to *IN36 if it is 24 or '0' will be assigned to *IN36
if it is
not 24.

Please let me know if I am not understanding the question.


Michele Cummings

WDT iSeries Development
IBM Toronto Lab



"Erich W. Schasse" <Schasse@Wiedemann.de>@midrange.com on 11/08/2001
08:38:29 AM

Please respond to code400-l@midrange.com

Sent by:  code400-l-admin@midrange.com


To:   "Code400-L" <code400-l@midrange.com>
cc:
Subject:  Cross Reference Problem


Hi folks,

I have a problem in CODE400 with the X-reference.

The variable VATEST in the following RPG IV statement will not be
recognized
in the result list.

    EVAL      *IN36 = (VATEST = 24)

Is there any patch available?

I would appreciate any hint because this function is importent for us.

 WDT400:        V5R1, SP3
 PC:                      Win2K, SP2
 OS400:         V4R5M0

TIA

Kind regards

Erich W. Schasse
WIEDEMANN
Wiedemannstr.

31157 Sarstedt

Tel.: 05066/997-190
Fax.: 05066/997-107
Mail Schasse@wiedemann.de <mailto:Schasse@wiedemann.de>


_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.







_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) digest list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.