RE: Mixing Subroutines & Sub-Procedures.

Yeah. I did that. Works fine. 

The philosophical question now is, what is the point of EXSR when a
procedure without parameters or return value can operate in exactly the
same way as a subroutine because of global scope? I guess it's backward
compatibility, and the slightly more difficult requirement of needing a
prototype declaration even though there are no parameters.

The manual states that there is a performance hit with the procedure but
doesn't say how much of a hit. Anyone have a figure?


I try and avoid holly wars. I always get pricked when they break out!

Thanks again.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Pantzopoulos -
(H/O)
Sent: Tuesday, 23 August 2005 4:12 PM
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

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