Re^3: use statement seemingly ignored

Does this not tell us that the function is not only not imported, but not even defined

The error message from the OP tells us it wasn't defined.

Neither the error message or the fact that using the full qualified name works tells us whether it was imported or not.

But it does strongly suggest the problem is that it wasn't imported, yes. The two most likely causes of that is buggy/missing exporting logic, or modules that (directly or indirectly) use each other.

Comment on Re^3: use statement seemingly ignored Download Code

Replies are listed 'Best First'.
Re^4: use statement seemingly ignored by BillKSmith (Monsignor) on Nov 22, 2022 at 20:55 UTC
I seem to have been a bit careless in my use of the word 'defined'. The original error message tells us that the function 'getMeetInfo' was not defined in the namespace `NCPS::Results`. This means that it was not successfully imported from the module NCPS::Meets. The [almost] same error message from the workaround with the fully qualified name tells us that the function is not even defined in own namespace. There is no function to import. (It is unlikely that the `NCPS::Meets` module is even loaded.) We should look for the error in the way modules are loaded, before even considering the way functions are imported. The existing maze of nested BEGIN blocks is probably an incorrect attempt to allow modules to use each other. Bill	[reply] [d/l] [select]
Re^5: use statement seemingly ignored by ikegami (Patriarch) on Nov 23, 2022 at 13:58 UTC
oh, I misread. I thought you said it worked when using the full name. Yeah, if using the full name doesn't work, then when I said doesn't apply.	[reply]