After further tests I found, if you use a Static function, AND you want to access it from outside the procedure file, then you MUST use a ModuleName pragma. Try the following in the procedure window:

Function TestMe()
 
	print "Hello World!"
	testyou()
	return 0
end
 
Static Function TestYou()
 
	print "Hello Universe!"
	return 0
end

Executing testme() on the command line works to print "Hello World!" and "Hello Universe!", however testyou() is inaccessible at the command line level. Putting this code into a Procedure window with a ModuleName=Tester pragma makes Tester#TestYou() accessible and keeps the simple call TestMe() still accessible.

So, with regard to naming functions to avoid conflicts ...

1) In any type of procedure file, the names of Static functions are always local.
2) When a procedure file or files have a ModuleName pragma, the names of Non-Static functions are still global.
3) When a procedure file or files have an IndependentModule pragma, the names of all functions are local.

When a function name is global, you should use a unique name (ie, GXY_Create(...) rather than Create(...)) to avoid potential conflicts with a (global) function using the same name in a different procedure file. When a function name is local, you can use any name you want.

Also, with regard to interactions of ModuleName and IndependentModule pragmas with Static or Non-Static functions ...

1) When a procedure file or files have a ModuleName pragma, you access Static functions from outside the module using the ModuleName#FunctionName(...) syntax.
2) When a procedure file or files have an IndependentModule pragma, you access any function from outside the independent module using the IndependentModuleName#FunctionName(...) syntax.
3) When a procedure file or files have both a ModuleName and an IndependentModule pragma, you access Non-Static functions from outside the module using the IndependentModuleName#FunctionName(...) syntax.
4) When a procedure file or files have both a ModuleName and an IndependentModule pragma, you access Static functions from outside the module using the IndependentModuleName#ModuleName#FunctionName(...) syntax.

Remember, when you design controls on control panels, their procedure files run as though they were called from outside the procedure file. Therefore, you must use the corresponding IndependentModuleName#FunctionName, ModuleName#FunctionName, or IndependentModuleName#ModuleName#FunctionName syntax.

(Just thought I would be expansive for the sake of anyone reading this who is new to Igor programming)

My tests show, you CANNOT use IgorMenuHook(...) from within an IndependentModule. Apparently, it is never called.

Perhaps, short of breaking the procedure file into two pieces (Regular with the IgorMenuHook(...) function and IndependentModule with everything else), someone has a suggestion on how to have an IgorMenuHook(...) function recognized when it is within a procedure that is an IndependentModule.

Alternatively, the inaccessibility of Igor hook functions might be a fifth Limitations of Independent Modules to add to page IV-41 of the manual.

--
J. J. Weimer
Chemistry / Chemical & Materials Engineering, UAH