Re: Protected Prototypes

That's right -- the export keyword gets your procedure visible outside your
module. The binder code for the service program gets the procedure visible
outside the service program. If you export from the module, but not from
the service program, you've got a procedure that's available to all inside
the service program but not available outside it.

Stu


On Thu, Feb 25, 2010 at 17:21, Simon Coulter <shc@xxxxxxxxxxxxxxxxx> wrote:

On 26/02/2010, at 10:00 AM, Kurt Anderson wrote:

Am I missing something obvious? I don't have this procedure in the
binding directory

You don't list procedures in binding directories anyway. They only
contain *MODULE and/or *SRVPGM objects.

and it does not have the Export keyword.

It needs EXPORT to make it visible outside the *MODULE. Whether it is
also visible outside the *SRVPGM depends on the binder source (or the
use of EXPORT(*ALL) which should be avoided)

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------



--
This is the RPG programming on the IBM i / System i (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.