Also, it's a tiny bit weird to have `Namespace Microsoft.SmallVisualBasic` since as best I can tell this is not a Microsoft project. Wouldn't `Namespace VBAndCs.SmallVisualBasic` work just as well and be less confusing?
"An enhanced compiler (yet easier for children and beginners) based on Small Basic, with a form designer and a mini Winforms lib. In short, I made small basic visual , so it became Visual small Basic, or in fact Small Visual Basic as it became a tiny dynamic version of VB6!"
Because the typing is still dynamic, I'd wager. In .NET you can have `dynamic` objects with arbitrary properties/methods/etc (although you are of course going to run the risk of runtime errors rather than compiler errors.)
This is also supported via ExpandoObject, which in most CLR languages has sugar to allow for dynamic declaration of properties/etc. [1]
Also, it's a tiny bit weird to have `Namespace Microsoft.SmallVisualBasic` since as best I can tell this is not a Microsoft project. Wouldn't `Namespace VBAndCs.SmallVisualBasic` work just as well and be less confusing?