|
Has anyone else noticed this oddity? If you have a comment line, the indenting of the next statement does not respect the previous "real" statement indent - or the comment indent either.
Example:
SUBR SUBR(MySubr)
IF COND(...) THEN(DO)
<some code>
ENDDO
/* Comment */
IF COND(...) <- this line will NOT indent to align with block above
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Tuesday, December 05, 2017 6:55 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Show block nesting in CLLE source
Hi Dan
Have you tried the indenting of blocks for CL? It's in a preference. If
you need to get the whole member to be indented with it, you can try
putting LL on the first line and LL and the last line - the indent takes
place in changed lines, and this changes the whole thing.
There can be places where the indent isn't what is expected - I have to
make some local adjustments, then get back to doing sections as needed.
You could do this on a copy of the member, if you want to maintain the
original layout. Just be sure to turn the indenting off if you need to.
HTH
Vern
On 12/5/2017 5:50 PM, Dan wrote:
I need to see the block nesting in a large CL source member. I have RDi
v9.5.1.1 and am attempting to use the same named function from the context
menu, but it is giving me "EVFG0102 Matching statement not found." The
source member compiles with no errors other than warnings about
unreferenced variables.
Google is not my friend.
Would really like to see the block nesting in the source editor, but I'll
take a solution that is view only. Ideally, I'd love to be able to
restrict a search within a selected block.
- Dan
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.