RE: Parameter Procedure return value in the parm list (WDSCi)

I have to agree with this somewhat.  I really like the features in WDSC. In
fact, feature-wise...WDSC has SEU beat 9 ways to Sunday.

However... WDSC is too slow for me to be productive with.  I don't know if
it's because I work remotely from my office 99% of the time, and working
over a VPN is the bottleneck with WDSC or what.  What I do know is that it
can take upwards of five minutes to load a relatively small source member
into WDSC on my workstation.   If I use SEU and Client Access 5250, I can
open the source member, make all the changes and recompile and STILL have
time left over to read the newspaper before the source finishes loading in
WDSC.

I don't think it's my network, although I guess it could be. But all my
other network traffic for everything else is fine, performance-wise. It is
only WDSC that seems to be unbelievably slow.  

It's entirely possible that if I was working on site that I'd have better
response times with it, but since I don't...I seldom have the patience to
use WDSC for something I can do faster and easier in SEU.

Shannon ODonnell



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Christen, Duane J.
Sent: Thursday, April 21, 2005 3:46 PM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Parameter Procedure return value in the parm list (WDSCi)

Charles;

Not to start a holy war, but you're wrong. I have coded "true" RPG IV using
SEU for nearly 6 years, C and MI for much longer than that. This year my new
years resolution was to become fluent coding with WDSC. After 4 months of
considerable effort I can still code 2 to 3 times faster in SEU than I can
with WDSC, and I'm being conservative. I have had some downtime the last two
weeks and have forced myself to use ONLY WDSC, no green screens, to develop
some maintenance programs. It should have only taken a week, I am not even
half finished and tomorrow is the end of the second week.

Yes WDSC does some nice things but as with every Windblows based software it
is as intuitive as the U.S. tax code and as user friendly as an electrified
razor wire fence IMO.  

Duane Christen


-----Original Message-----
From: Wilt, Charles [mailto:CWilt@xxxxxxxxxxxx]
Sent: Thursday, April 21, 2005 2:19 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Parameter Procedure return value in the parm list


> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Kurt Anderson
> Sent: Thursday, April 21, 2005 3:00 PM
> To: RPG programming on the AS400 / iSeries
> Subject: RE: Parameter Procedure return value in the parm list
> 
> 
> Charles,
> 
> I realize that the prototype tells you all you need to know, 
> but ideally
> I'd like the code to tell me that.  Such as, in your example...
>       CalcTax( orderAmt : taxAmt ); 
> ... The amount being changed here is not explicit.  As a programmer I
> now need to page up or whatever to find the prototype to see which
> field, if any, is being changed.  This is what I'd like to get around
> (w/o writing comments).

Ah, but if you're using WDSC, then the outline view shows you which params
are VALUE or CONST.  No need to page the source itself up.

My personal mantra...if you're trying to use SEU to do true RPG IV
programming...you're wrong.
Two main reasons:
1) The usefulness of the outline view
2) How easy "Auto-Complete" aka "Code Assist" makes it to use longer names.




NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named.  Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.



-- 
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.