Re: SEU vs. ?

SEU hasn't changed a bit in the last 12 years (or more). There are a lot of
things that modern editors can do and SEU can't. Furthermore there are a lot
of things I have to type that could also be selected form a list. I.e.
filenames and fieldnames. Why doesn't SEU have a proper undo function, color
coding, nesting info, source navigation, automatic opcode completion, etc?
The iSeries knows the description of a field. Then why can't SEU show me
that information when I use that field in a statement? Why can't SEU put the
fielddescription in the comment field when I want?
There are a lot of products that provide some of these features. Editor/400
has those features, why hasn't SEU?
It still amazes me.

Wilbert
www.statement400.com

----- Original Message ----- 
From: "Joe Giusto" <jgiusto@xxxxxxxxxxxxxx>
To: "'RPG programming on the AS400 / iSeries'" <rpg400-l@xxxxxxxxxxxx>
Sent: Monday, June 02, 2003 11:44 PM
Subject: SEU vs. ?


> Outside of a few glitches in syntax checking (and by the way it seems to
> handle COBOL multiple line statements just fine), what is all that wrong
> with using SEU.
>
>
>  -----Original Message-----
> Subject: RE: ACK!  What happened to ...?
>
> I really want to thank all of you for suggestions to get the last
> dinosaurs to move from SEU:
> - make huge monolithic programs
> - Use large procedure names that continue on to the next line
>
> :-)
>
>
>
>
> _______________________________________________
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.