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



Actually, in my opinion, it's the local variables that make code more
bug-prone. Why on earth do I need to keep track of what the variable is in
this or that procedure, anyway?

On Mon, Mar 31, 2008 at 11:38 AM, Steve Richter <stephenrichter@xxxxxxxxx>
wrote:

On Mon, Mar 31, 2008 at 12:18 PM, Bob P. Roche <BRoche@xxxxxxxxxxxxxxxxx>
wrote:

But *PSSR is there to handle things that are unexpected. If an error is
possibly expected, definitely use MONITOR. I also don't see the problem
with *INZSR, why get rid of a subroutine, just because it s a
subroutine?
I agree there are times when *INZSR should not be used but just to
replace
it with a named procedure, just so you don't have a subroutine, I don't
see the point. procedures and subroutines both have their uses.


Bob,

I dont think I have written a subroutine in /free, ever. The problem with
subroutines is they require global variables. Globals are bugs waiting to
happen. They make code very difficult to read and modify.
--
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.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.