Re: EXPORTing subprocedures

On 2024-05-15 12:15 p.m., Jon Paris wrote:

Interesting Brian,

Perhaps Barbara will pop-in and explain (or tell us it is a bug) - but the "cure" is to remove your proto for the Msg() routine. I never code those anyway since they became optional so it is not a situation I would normally encounter.

Remove the Pr and the bind error disappears and all works as expected.

...

If you have a PR for a procedure in the module, it should be a global PR, to match the procedure which is also global within the module.

When you have a PR inside a procedure, it is a local prototype, private to that procedure. The compiler doesn't consider whether it is a procedure within the module, so it gets listed as an import when you create the module. That's why it works when you export the procedure.

The solution is to either move the prototype out of the linear main procedure or just remove the prototype entirely.