Re: RDi 9.5 announcement

Even in VB one is encouraged to use continuation markers instead of carrying strings out to forever. I would strongly suggest the same thing here, but the length before needing the continuation can be a full screen-width on a larger monitor.

Someone mentioned word-wrap = it is being done now in the SQL statement support, and it is also done in the CLP/CLLE editor - maybe? I don't remember seeing it in the beta.

I would be hard pressed to get a full 32,766-long line of code, unless building some very long piece of HTML or XML, eh? But I'd still find a reasonable length that I'd be able to manage.

Back to real work!
Vern

On 9/2/2015 11:11 AM, Dan wrote:

I understand the existing 80-column limit was arbitrary / legacy and, since
the community was clamoring for 100 columns, it was probably just as easy,
technically, to open it all the way up to 32766, so, why not? If
developers want to shoot themselves in the foot, let 'em.

Of course, if I need to maintain / fix someone else's mess in 32k column
source, someone's gonna get a thrashing.

- Dan

On Wed, Sep 2, 2015 at 11:40 AM, Koester, Michael <mkoester@xxxxxxxxxxxxx>
wrote:

PDM has a limit of 240 characters that it can process, which is a record
length of 252. CTRSRCPF allows record lengths up to 32,766 which CAN be
edited in RDi and for the full length in the new regime. Before the

change

upcoming, even with a longer record, only positions 8-80 could be used

for

code.

Vern, I'm all for the idea of more than 80, but if I ever had to read code
statements longer than about 120, I'd require a wrap-around panoramic
monitor (the single 21" flat screen just wouldn't cut it). Let's keep it
within a comfortable field of view, please. Just because we can doesn't
mean we should.

Michael Koester