Re: Multiple issues with CL Source editing

For the time being, I keep mine at 100 for two reasons:

1) On occasion, I will print source members via SEU. When a line extends
past column 100, it wraps to a new line, which is annoying to read,
especially when it splits something in half to print it.

2) While RDi can scroll left and right, I prefer not to deal with that. I
am an old-school keyboardist at heart, and I like to see all columns of
code without having to scroll. My current monitor, with the default RSE
panes, allows 100 character lines in the editor that are readable to me.
Perhaps if we ever get monitor upgrades, I could be persuaded to use longer
lines.

2a) I just remembered that I can maximize the editor pane; and it appears
that it can show about 160 characters per line. Hmmm...

- Dan

On Tue, Sep 5, 2017 at 2:06 PM, Duane Scott <dscott@xxxxxxxxxxx> wrote:

Dan,

I had been using 100 for years before coming here. I never even thought
to look until my compiler started choking on missing source. Surprise,
surprise.

I'm thinking that 100 is going to be the standard here unless somebody
convinces me or my handlers that a larger number is better.

Thanks

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan
Sent: Tuesday, September 5, 2017 1:12 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Multiple issues with CL Source editing

On Tue, Sep 5, 2017 at 11:24 AM, Duane Scott <dscott@xxxxxxxxxxx> wrote:

Third is the problem of what to set as the record length for the CL
Source file. Since the compiler will accept 100 column commands, and
the settings on RDi are "*RCDLEN", "80" and "100", one would think
that the new record length for CL Source Files should be 112. But
record length for CL is not specifically discussed in more recent issues

of manuals that I could find.

RPG has quite a few discussions of longer settings being available.
I'm not sure if we should stick to 80, move to 100, or go beyond. The
fact that some of our programmers and operations staff still use SEU
is of issue, but I'd like to hear some other viewpoints.

I've been using 100-character source lines (record length=112) for CL for
at least several years now. I really can't remember when/if the compiler
ever choked at anything past column 80. It's true that the command
prompter in SEU always formats assuming 80-character length, but that never
meant that you couldn't code anything yourself after column 80.

- Dan
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list To post a message
email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
CONFIDENTIALITY NOTICE: This electronic message transmission is intended
only for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. If you have received this transmission, but are not the
intended recipient, you are hereby notified that any disclosure, copying,
distribution or use of the contents of this information is strictly
prohibited. If you have received this e-mail in error, please contact NALC
Health Benefit Plan at 703-729-4677 and delete and destroy the original
message and all copies.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.