RE: Subroutines vs Subprocedures was RE: Indicators

I see what you are saying.
But when it comes to having a return exit the program and not the 
subprocedure, that's one advantage that a subroutine has.
Granted, it's probably a violation of structured programming.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Lim Hock-Chai" <Lim.Hock-Chai@xxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
08/19/2004 02:22 PM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
"RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
cc

Fax to

Subject
RE: Subroutines vs Subprocedures was RE: Indicators






I don't see a reason to use sub-routine at all.  Sub-procedure can not 
exsr to main procecdure's sub-routine.  If you mix them, you might endup 
have to change sub-routine to sub-procedure because of that.


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of
michaelr_41@xxxxxxxxxxxxxx
Sent: Thursday, August 19, 2004 2:10 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Subroutines vs Subprocedures was RE: Indicators


It's all a matter of where you want to break the code. I tend to make
subprocedures more generic and subroutines more specific.

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