Re: Resistance to using RDi

Agreed.

I also find that outline is invaluable when a large number of /Copy protos and contestants are in the mix. One project I’m working on has literally hundreds of protos, DS templates, and constants. Even though the code I’m writing may only be a couple of hundred lines it is still useful to know which functions I need, what the DS comprise and what parms are needed. Similarly for field from external print files etc.

Only time I _don’t_ need it is when writing a simple proof-of-concept or snippet for a magazine article etc.

On Feb 23, 2016, at 4:38 PM, Sam_L <lennon_s_j@xxxxxxxxxxx> 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.

(Though I also like it for new code...)

Sam

On 2/23/2016 3:10 AM, Scott Klement wrote:

People gush about stuff like the outline view, ... I think it's mainly useful if you're
stuck in a shop that writes ancient, hard-to-decipher, code.

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

Jon Paris

www.partner400.com
www.SystemiDeveloper.com