Re: RDi: 3rd party source code formatters

SQL formatter options:
Automatic uppercasing: on, custom, uppercase, lowercase.
Formatting: on, indent 2, new line after, new line before
Treat text beyond column 80: on
Use enhanced formatter: on

LPEX:
Show date area: on
Column-sensitive editing: on

Observations:

1. When I update source I haven't touched in a few years, everything
appears to work exactly as expected.
2. IMO, well-formatted code is *much* easier to spot subtle coding
errors, *much* easier to debug, and *much* easier to understand by the
programmer looking at the code for the first time.
3. IMO, A good code formatter is an important development tool, like a
non-functional requirement: you can't put your finger on what it's doing
but you know it's important.
4. There are cases (an SQL pun) where manual formatting conveys the
purpose of the code better than auto-formatted code, especially when doing
conditional WHERE's and ORDER BY's.

Questions: is there a cache or work folder we should be clearing
periodically? Should I create a new workspace periodically?

Thank you!

On Wed, Mar 15, 2023 at 8:32 AM Mike Hockings <hockings@xxxxxxxxxx> wrote:

What are your formatting settings? I thought the default now in RDI was
to use the SQL formatter in ACS?

Mike

---
Mike Hockings, M.Eng.
IBM Rational Developer for System z and Power Systems Software Technical
Support
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
voice 1-905-413-3199 T/L 313-3199 ITN 23133199



From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Reeve <
rfritchman@xxxxxxxxx>
Date: Wednesday, March 15, 2023 at 07:46
To: wdsci-l@xxxxxxxxxxxxxxxxxx <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] [WDSCI-L] RDi: 3rd party source code formatters
I'm looking for a free 3rd party source code/SQL formatter I can plug into
RDi. The built-in hasn't worked well or consistently for years and I'm on
9.6.0.12. I guess cleaning this up isn't a high priority for the RDi team.

The SQL formatting drives me bonkers. I frequently get "Could not indent
source beyond end column limit 80" messages. In addition, blank lines are
often deleted and the casing of structured opcodes usually goes to ALL
UPPER if the preceding SQL statement is malformed. The SQL formatter in
iACS is pretty good but then there's no RPG support; why not port that
code?

I can take a few days and write one myself but, like everybody else, I have
other things to do. But it would be fun, so I better stop talking about
doing it before it becomes too enticing.

--reeve
--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l .

--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.