RE: Mixing Subroutines & Sub-Procedures.

I think you have just started a holly war... :).

A subroutine in the main procedure is only visible to the main procedure.  
Likewise, a subroutine in a sub-procedure only visible to that subprocedure.  
Your choice would be, either convert the subroutine to subprocedure or change 
your subprocedure to subroutine.

That is one of the main reason that I think IT shop should restrict usage of 
subroutine in main procedure.  Yes, I know there are some instant that it make 
sense.  However, I see it do more harm than good.



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Mike Pantzopoulos -
(H/O)
Sent: Tuesday, August 23, 2005 1:12 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Mixing Subroutines & Sub-Procedures.


I created a simple sub-procedure in an existing program, and tried to
reference an existing subroutine. The compiler didn't recognize the
subroutine reference. I thought it might be a scope issue and so took a
copy of the subroutine code and copied it into the body of the procedure
just before the Procedure End statement.  
The program worked.

I then removed the code for the subroutine from tha main body of code.
No good. The compiler couldn't see the subroutine sitting in the body of
the sub-procedure. Presumably because of scope again.

The problem now is that I have the same code in two places in the
program. 

Is there an easy way out?



Mike Pantzopoulos
EIG-Ansvar Limited
Tel  : 61 (3) 9614 3535
Fax: 61 (3) 9614 2740



*********************************************************************************************************
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you are not the intended recipient, any use, disclosure or copying of this 
message is unauthorised. If you have received this message in error, please 
reply using the sender's email address. 

This footnote confirms that this email message has been scanned for computer 
viruses. EIG-Ansvar Limited does not accept liability for any loss or damage, 
whether caused by our own negligence or not, that results from a computer virus 
or defect in the transmission of this email or any attached file. 
EIG-Ansvar Limited - Australia (A.B.N. 21 007 216 506)
Email : insure@xxxxxxxxxxxxxxxx

Eig-Ansvar Limited - New Zealand
Email : insure@xxxxxxxxxxxxxxxx

*********************************************************************************************************