|
Make your code shorter, but yeah, I'd vote for this. On Tue, May 12, 2015 at 9:45 AM, Koester, Michael <mkoester@xxxxxxxxxxxxx> wrote: > Perhaps there's a setting, or an open RFE for this, or maybe it's already > available in a newer RDi version (currently running 9.1.1)? > Some of my RPG source members are a bit long, and within them, some of the > subroutines and subprocedures are also a bit long. I often wonder > (particularly when I'm searching for occurrences of global variables) where > I am in the source. The line number tells me I'm in deep, but... Which > subroutine or subprocedure am I looking at LPEX, and how would I know > without having to scroll up to find the begsr or P-spec? > If I'm the first to bring this up, and if I'm not the only one on Planet i > for whom a solution would be helpful, I'd be happy to offer an RFE to show > the name of the subroutine or inline subprocedure where the cursor is > located. Could be displayed at the top of the LPEX pane to the right of > the "Line 1187 Column 8 Replace". Perhaps right-adjusted to the far > right of the visible window? Or on the very bottom line of the editor, > between the last visible source statement and the command line? > Any support for this? > > Michael Koester > Programmer/Analyst > DataEast - Granite State Communications > > -- > 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.