× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



"Anybody still have to deal with TAGs & GOTOs? New RFE..."
https://archive.midrange.com/wdsci-l/201611/msg00025.html

If so, vote for my RFE
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=96699

Charles

On Tue, Mar 21, 2017 at 10:06 AM, Jim Hawkins <jhawkins@xxxxxxxxxxxx> wrote:

I know no one uses GOTO anymore but one of my predecessors wrote a lot of
code using RPGII style (conditioning indicator, goto, etc.) in RPGIV
format.
Found an issue this week that was losing information periodically that I
was
able to fix without too much issue. But the code was littered with "goto
exit" statements. (This code was last updated in 1999 to Y2k compliant).
I tried to find this EXIT in the outline view to see where all of these
were
sending the logic flow. It took a while but I found it. Is there a good
way
to find the where a GOTO is going to end up? I was hoping to find them in
outline view.
TIA
Jim Hawkins

--
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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.