Giving module a name that does not correspond to its filename seems to cause its definitions not to be made vvisible in importing module. No error is given about wrong name.

Submitted by Eelco Visser on 6 November 2010 at 12:03

Warnings are now triggered when module/application name does not match file name/path.