[mono-vb] Microsoft.VisualBasic namespace

Eric Mutta Anon21h@yahoo.co.uk
Tue, 08 Jun 2004 01:19:02 +0100


Hi everyone,

Good to see progress is being made on the VB side of things...comments 
are inline.

A Rafael D Teixeira wrote:
 > On Mon, 2004-06-07 at 07:12, Jochen Wezel wrote:

<snip>

 >>Is it a just-in-time-wrapping in the compiler of a defined list
 >>of methods to another namespace/module, in this case Strings.ChrW?
 >
 >
 > In truth as Strings is a vb "Module" it is normally ommited, because all
 > methods/properties/fields defined in them are static and given global
 > visibility where the namespace is available. I've been working on this
 > bug and resolved the most part of it, but I could not make it work for
 > this specific case when the method is just semi-qualified with just
 > the namespace.

Rafael, I'm not sure how you currently do symbol look-up in mbas, but 
couldn't the above situation be handled via a breadth-first search on 
the module names first then the names of members within the modules?
This can be done very rapidly if you use scoped symbol tables.

 > That is why the corresponding bugzilla case is still open.
 > Most people won't experience the problem because normally they would
 > write just
 >
 >         Console.WriteLine(ChrW(89))
 >

I personally do an:

    Imports strs = Microsoft.VisualBasic.Strings

then use:

    Console.WriteLine(strs.ChrW(89))	

which I believe mbas handles just fine right now(?).

Cheers,
Eric.