Bugzilla – Bug 313342
Public Definitions in Module have to be treated as global symbols
Last modified: 2007-09-15 21:24:23 UTC
---- Reported by rafaelteixeirabr@hotmail.com 2003-12-11 15:57:10 MST ---- Please fill in this template when reporting a bug, unless you know what you are doing. Description of Problem: mbas cant compile this code :/ == module1.vb == Imports Microsoft.VisualBasic.Strings Imports System.Windows.Forms Module Module1 Sub Main() Console.WriteLine(Right(Application.StartupPath, 1)) End Sub End Module Actual Results: >mbas /r:System.Windows.Forms.dll module1.vb module1.vb(8) error BC0103: The name `Right' could not be found in `Module1' Compilation failed: 1 Error(s), 0 warnings Expected Results: How often does this happen? always Additional Information: Any public definitions in vb "Modules", need to be name resolved without needing the module name as if they where "global" symbols. This is an old problem, not yet tackled by us... ---- Additional Comments From banirban@novell.com 2004-07-08 10:11:59 MST ---- Just now I closed one bug (60399). That fix seems to have completed the last part of this fix too. If there is no further issue left we can close this bug too. ---- Additional Comments From rafaelteixeirabr@hotmail.com 2004-07-12 10:25:14 MST ---- Tested Anirban latest patch and now the Semiqualified form works. So We have it. Kudos!!! Unknown operating system unknown. Setting to default OS "Other". Skipping unknown keyword: parity. Skipping unknown keyword: task.