RE: Tabs in SEU -- MIDRANGE-L

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
I had a gent here who wasted 45 minutes trying to debug a CL program.  He
used SEU.  Soon as I pulled in up in Code/400 I could see the problem
immediately.  The line he thought was doing something was actually a
comment.  Simple things like color actually do make a huge difference.

The debate of bug versus limitations can boil down to being as mindless as
the debate of whether something is a virus or a trojan.  The end result is
the same.

Let's say that you kept getting MCH errors, reported it to IBM and got
'Working as designed'.  Would that then be a bug or a limitation?  If it
is truly 'working as designed' you could monitor for this message and
process it accordingly.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




"Tyler, Matt" <mattt@wincofoods.com>
Sent by: midrange-l-admin@midrange.com
10/10/2002 01:46 PM
Please respond to midrange-l


        To:     "'midrange-l@midrange.com'" <midrange-l@midrange.com>
        cc:
        Fax to:
        Subject:        RE: Tabs in SEU


Rob,
                 No one is trying to bash your point of view.  It's just
that, in my
experiences, CODE/400 has not offered anything to actually enhance the
coding experience.  You can code off-line but you still have to get
on-line
to verify the program and get cross-reference.  So, are these bugs? I say
no, just limitations of the software designs.  To my a bug is logic that
does something you did not intend it to do or did something you thought it
would not do that caused a program exception or data issues.

                 I think everyone should try CODE/400 for them selves, but
I just
want to warn others that it is not the fix for all dislikes with SEU. Both
have limitations that need to be resolved and we all suspect that IBM will
no longer update SEU with new features, beyond the exit points.


Thank you,
Matt Tyler
Mattt@wincofoods.com

-----Original Message-----
From: rob@dekko.com [mailto:rob@dekko.com]
Sent: Thursday, October 10, 2002 12:34
To: midrange-l@midrange.com
Subject: RE: Tabs in SEU

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Didn't I say earlier that people would say they weren't bugs?   :-)

However if we looked at them as such then we would think SEU is extremely
buggy compared to Code/400.

Which is likely to have more problems:  a stone knife or a chain saw with
all the latest features?  If you had to cut down a forest... oh the heck
with it.  everytime someone tries analogies on this list they get ripped
apart.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




"Joe Pluta" <joepluta@PlutaBrothers.com>
Sent by: midrange-l-admin@midrange.com
10/10/2002 12:51 PM
Please respond to midrange-l


        To:     <midrange-l@midrange.com>
        cc:
        Fax to:
        Subject:        RE: Tabs in SEU


> From: rob@dekko.com
>
> The list is not quite the biblical 7 x 70 but a very small
representative
> sample of SEU bugs include:
> - It doesn't automatically color your source based on the type of the
line
> and the keywords included on the line
> - I can't work offline from the host

These aren't bugs.


> Yes you can recover.  It's just done differently.

With SEU it's automatic.  Sign back on, go to edit the member, and you're
there.


I guess the point is that different tools do different things...
differently.  Some better, some worse.  For me, SEU is a better tool for
much of the source entry I do.  I just wanted to know what bugs you were
running into.

Joe

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.