I.e. it should be an error to declare as local a name that has
already been declared as global.
I don't see how that could be a portable solution.
Say a module uses the name 'FFT' as a local variable and you declare 'FFT' to be a global in your app that references that module. Should the module fail to load because it uses a local FFT?
Derek