Overview |
The intricate design of our brain is still a source of wonder and amazement,
and with some old programs that occasionally come up for maintenance you
may wonder whether there was ever any design to begin with. THE Editor's
Choice will help you comprehend even those relics from the Ark.
|
|
Navigation
Source Entry
 Downloads
|
 Filtering
To understand what a program is doing, it would be great if you could
block out all the superfluous statements and just view say all the decision
type statements. (i.e.: The IF's, DO's, etc.)
With just the press of an Fn. key THE Editor's Choice does this for you.
Each RPG Op code is assigned to a generic statement type. When filtering
is active, only the generic statement types you selected are displayed
in the edit window.
You can also change the generic types included to suite different needs.
For example, in one session you may want to include I/O statements, while
later in another session exclude them.
In DDS source members, filtering can be used to display just the record
and field definitions - very useful for DSPF and PRTF members.
|
 Home |
 If/Do Level
RPG compile listings, and many PC based source editors shown the If/Do
level so you can match up the start and end of IF and DO constructs. This
is so essential to code comprehension that we couldn't leave it out. So
now those old spaghetti monoliths you have to maintain once in a while
will strike terror in your heart no longer.
When used with filtering and the Jump (to a code segment) command, you
can tackle those old monsters with confidence.
In 80-column mode, source change dates may alternatively be displayed
in this column, allowing the source data window to start in any position.
|
| |
Color
Have you ever taken hours to track down a silly bug, only to find that
at the end it was because a statement had been commented out with just
a single *? Well we haven't for years, and you don't need to be caught
out from now on.
For RPG and CL, comment statements with valid Op codes or commands are
displayed in the color of your choice. You can choose your preferred colors
for statements, comments, and deleted Op codes, as well as highlighted
comments (e.g.: subroutine headings).
Even if you have a monochrome screen, THE Editor's Choice will allow
you to select display attributes so that you can quickly distinguish code
from comments.
|
| |
Held lines
Let's say your looking at an I/O statement that uses a key list that
is defined elsewhere. You jump to the key list and it has half a dozen
fields of very similar characters. It would be neat if you could hold
those statements in the edit area and return to the I/O code. THE Editor's
choice does just that.
What's more, if one of those key fields is wrong, you can change it right
there, you don't even need to return to the KLIST statement.
|
| |
Browse with compare
Try spotting the difference of just one or two characters between the
edit and browse windows, and you will just love this feature. Just turn
on compare, and the Editor's Choice will do it for you, both faster and
more accurately.
It didn't take us long to realize that this is not very useful unless
you can roll both edit and browse windows simultaneously, so turn on Track
as well, and a single press of Page-Up and both windows will roll together.
In case you have been using a tool that places the If/Do level in the
C-spec comment section, compare can operate on a specified column range,
e.g.: 7 thru 59 for RPG III.
|
| |
Compile errors
Compile errors in a spool file are loaded into the edit area. These additional
statements cannot be accessed, nor are they copied back to the source
file. The advantage of not using the browse window, is that it allows
the browse window to be used to view another source member. Note: Spool
files can still be displayed in browse mode.
Compile errors can also be loaded from the compiler output file (*PGM
objects only) instead of from the spool file. It is much faster to read
just a couple of database records than 100 pages of spool file to find
that one terminal error.
|
