Re: ADTS V6R1 - No SEU updates?

Actually, I can kind of see IBM's logic.

At v6r1, you've got two tool choices, SEU or RDi. Both of which you have to pay for. Thus those are
the two tools IBM updated.

Personally, I'd like to see them just drop SEU.

The SEU vs. WDSCi/RDi battle is a silly waste of time to be fighting in this day and age; which is
made even worse by the v6r1 changes.

If you have to edit code while in a restricted state, or for some other reason can't use RDi, then
there is always EDTF.


Charles Wilt
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307

wiltc@xxxxxxxxxx

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Jon Paris
Sent: Thursday, February 14, 2008 2:37 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] ADTS V6R1 - No SEU updates?


On 14-Feb-08, at 11:39 AM, wdsci-l-request@xxxxxxxxxxxx wrote:

Be careful defining the term "Stabilized, Jon. George specifically
called WDSC "stabilized", and by that he meant no changes whatsoever
other than bug fixes.

I was being careful Joe - the normal meaning of stabilized in IBM is
fixes only - possibly more careful than George was <grin>. When a
fundamental change is made (e.g. the addition of a new data type to
DDS or a change in language syntax) then stabilized tools either have
to offer a low-level accommodation of the change (as will happen when
new data types are introduced) or reject it in an organized way.
With SEU they have followed normal policy and updated the syntax
checker. With WDSC they have not. Two tools - same status -
different approach.

Don't get me wrong - I'm very much in favor of everybody switching to
RDi - the tools have to make money if we are to see progress. But
enabling SEU and not WDSC in my opinion was a poor choice. To enable
WDSC to use the RDi syntax checker/verifier should have been a
trivial task the two tools are fundamentally the same. Updating it
for SEU was almost certainly a lot more more work.

If RDi was a no-charge option this would not be an issue - but since
it has a charge people have to have time to budget for that. If I
have updated my compilers and everything else to V6 then I should be
able to use it. It makes no sense to support it in a 20 year old
tool and not in a 5 year old tool - particularly when the two tools
are so closely aligned.


Jon Paris

www.Partner400.com
www.SystemiDeveloper.com


--
This is the Websphere Development Studio Client for 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.

This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.