Re: RDi 9.5 announcement

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

True enough - I wasn't sure what you meant at first, Dan, but yes, newer 
syntax will raise the error in SEU. You CAN edit in there if you REALLY 
want, but you'd better be sure your syntax is right - SEU will NOT help you.

So in a way, I don't see post-6.1 as the nail - even the upcoming 
full-free (1-whatever columns) can be edited there, so long as you don't 
exceed the 252-byte record length (240 character limit to the data).

Trouble is, it is just harder and harder to justify to work in SEU - IF 
you are using more modern capabilities. The same idea applies to older 
versions of RDi (WDSC or RDp or whatever) - there is a constant flow of 
new stuff that the editor keeps us with, and older editors will not 
understand.

This is all GOOD STUFF!! Right? Just stay current on maintenance and we 
are good. This is not really any different from getting the latest 
version of the compilers in a licensed product like 57xx-WDS, seems to me.

On 9/2/2015 4:13 PM, Dan wrote:
> Correct.  SEU can handle up to 240 length, which, practically speaking,
> means that RPG syntax newer than v6r1 is *the* nail that shuts SEU's
> coffin, not the new 32766 "limit".
>
> - Dan
>
> On Wed, Sep 2, 2015 at 5:01 PM, Sam_L <lennon_s_j@xxxxxxxxxxx> wrote:
>
> > Did you mean SEU has a limit of 240 chars.  I wonder if increasing the
> > record length will mean that SEU will no longer be able to edit such source
> > files, regardless of syntax checking.  Another nail in the SEU coffin?
> > Interesting...
> >
> > Sam