|
On February 23, 2016 at 5:04 PM Buck Calabro <kc2hiz@xxxxxxxxx> wrote:Paul Therrien
In a different thread,
On 2/23/2016 4:38 PM, Sam_L wrote:
There is a lot of ancient, hard-to-decipher code out there that has to
be maintained. This is where, in my experience anyway, RDi, and the
outline view, really help. If you have such code, IMHO you need RDi.
I live and breathe this exact scenario. Code written in the S/36 days,
full of left hand indicators, GOTO nests and everything is a hodgepodge
of dodgy variable names like NUM, NUM1 and TEST.
I am clearly doing something wrong, because I find the outline view
close to useless. Only rarely does it match up to the compiler cross
reference, and in the middle of editing, it comes and goes as the parser
chews away on the code-in-progress.
I'm not complaining in the least bit: I see this as a work in progress,
and I do see it getting better with each release. My point isn't to
complain, it's to try to find out how other people keep finding the
value in it that I can't seem to.
For context, I've been using RDi and ancestors since Code/400 ran on
OS/2. I'm a happy, happy RDi user who keeps a compiler listing open on
the other monitor.
--
--buck
Visit wiki.midrange.com and register for an account. Edit a page that
helps you, and because it's public, you'll help someone else, too!
--
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 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.