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



Ah, I never said it was in the last twenty years. <wink> I mostly did it
in the days when RPG variables were limited to 6 characters and I was
documenting what variables were for API calls. (And that was not just
system API calls, but software vendor APIs--some of those were pretty
obscure.) I haven't even thought about using right-hand comments for a
while. I simply take another line and embed my comments in the main body
of the code.

But I wouldn't decry someone who uses right-hand comments. It's in the
documentation. The editor handles it. The compiler handles it. If you're
reworking code and can convert to free form, great! But there are times
when reformatting code for a small change simply hides what's been changed
in an existing program. So for fixed column coding, right-hand comments
don't bother me. Heck, I always appreciate when anyone gives a programmer
coming along later whatever help they can.

At any rate, I think we've wandered from Taryn's original post. (I'm not
just pointing at you John.) His request was for feedback on the RDi
automatic SQL formatter. As much as we like to think of RDi and the
compiler as all just part of IBM, they are separate units. If we argue for
a compiler enhancement, it side-steps the issue. Do we want the SQL
formatter changed? I personally would like to see the idea communicated by
Taryn come to pass.

IIRC, there is a compiler enhancement in the works. (There are always
enhancements in the works). But who knows when one related to this will be
done. This list really isn't the right place to campaign for compiler
enhancements. (Although there have been times I've voiced desire for them
on this list.)

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 06/13/2014 01:00:03 PM:
----- Message from "Voris, John" <john.voris@xxxxxxxxxxxxx> on Fri,
13 Jun 2014 15:39:04 +0000 -----

To:

"wdsci-l@xxxxxxxxxxxx" <wdsci-l@xxxxxxxxxxxx>

Subject:

[WDSCI-L] Feedback regarding the automatic SQL Formatter

My $ 0.02

I would say that Michael is an exception to have used right hand
comments anytime in the past 2 decades
Noone, noone noone for the past twenty years that I know has been
used the right hand side comment on the "C" spec . . .
Even though the RPG Manual has "The comments section of the
specification extends from position 81 to position 100"

And any kind of limit on a free form line (SQL or RPGLE ) because of
its indentations, would not make any sense.

So to summarize, it is . . .
Any comment on C*, or comment to the right of // should be the only
allowed comments
(and for the record, yes there is a comment section on the ** Array
spec)

Going beyond column 80 and assuming it is still allowed as a
comment, falls into the region of "Here there be monsters" on our pirate
maps.
So Yes, SQL statements that extend past column 80 should be allowed.

- John Voris

On 6/12/2014 3:58 PM, MichaelQuigley@xxxxxxxxxx wrote:
I have to confess I have used the space beyond column 80 for comments
at times--although it's been a while and I doubt that I ever used it
on SQL code. Regardless, I would rather be able to enter and have the
SQL properly automatically format than use the comment area.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.