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



On 9/3/2015 9:48 AM, John Yeung wrote:
On Thu, Sep 3, 2015 at 9:16 AM, Roche, Bob <broche@xxxxxxxxxxxxxxxxx> wrote:
Why do you not like sequence numbers? When there is a problem in the code, isn't it nice to have the system tell you where it is? It's not like RDI make syou look at them.

I think folks that don't like sequence numbers are specifically
against *stored* sequence numbers. Personally, I consider them to be
mostly harmless, but completely useless. I have auto-renumbering on,
and compiler listings have their own sequence number anyway.
-snip-
But for me, there is zero benefit. Display
of sequence numbers should be handled dynamically by the editor,

In RDi, one can disable displaying the sequence numbers:
Escape (to get to the command line)
set prefixAreaOff, Enter
Escape (to get back to editing)

If one likes this setting, one can build a profile that will set it
every time one opens a source member.

and
error messages should report the ordinal line number accordingly.

In RDi, clicking on an error message automatically brings you to the
line in error.

You can see in RPG IV compiler listings and dumps that IBM had
precisely this in mind.

I believe the compiler-generated line numbers are there to accommodate
I- and O-specifications 'generated' from externally defined files, as
well as source included via /COPY or /INCLUDE.


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.