×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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 mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
