[Mono-list] [mono-vb] [Mono-dev] Visual Basic upgrade.
rolfbasura at ya.com
Sat Aug 19 14:17:18 EDT 2006
The compiler is using just about every new feature
that came with VB8 (.NET v2.0), changing the compiler so that
it can compile with VB7 (.NET v1.1) will be much more work than
finding some other solution to emit 1.1 assemblies
(like using Cecil for instance).
>> > Hello,
>> > The vbnc compiler is currently emitting 2.0 assemblies, and regarding
>> > the two issues for it to emit 1.0/1.1 assemblies the first one is the
>> > easiest (the only feature that would have to be disabled is generics,
>> > VB8 does not support directly nullable types like C# - and if you
>> > disable generics you'll also disable nullable types since they are
>> > also generic). The rest of the new features in VB8 are just compiler
>> > features and are perfectly compatible with 1.0/1.1 assemblies.
>> > The second issue is that since the compiler can only run on the 2.0
>> > runtime it can only generate 2.0 assemblies with Reflection.Emit.
>> Why is this ? What 2.0-only features are you using ?
> Apart from generic SRE & reflection API's, that is.
> Would conditional compilation directives be a solution, or would it make
> code unmanageable ?
> Miguel, why wasn't this done for gmcs (instead of having to sync mcs
> changes) ?
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
More information about the Mono-list