[Mono-dev] [Mono-list] [mono-vb] Visual Basic upgrade.
gert.driesen at telenet.be
Sat Aug 19 11:26:37 EDT 2006
> -----Original Message-----
> From: Gert Driesen [mailto:gert.driesen at telenet.be]
> Sent: zaterdag 19 augustus 2006 17:08
> To: 'Rolf Bjarne'; 'Miguel de Icaza'
> Cc: 'mono-list at lists.ximian.com'; 'Jelmer Vernooij'; 'mono-
> vb at lists.ximian.com'; 'mono-devel-list at lists.ximian.com'
> Subject: RE: [Mono-list] [mono-vb] [Mono-dev] Visual Basic upgrade.
> > -----Original Message-----
> > From: mono-list-bounces at lists.ximian.com [mailto:mono-list-
> > bounces at lists.ximian.com] On Behalf Of Rolf Bjarne
> > Sent: donderdag 17 augustus 2006 12:52
> > To: Miguel de Icaza; Gert Driesen
> > Cc: mono-list at lists.ximian.com; 'Jelmer Vernooij'; mono-
> > vb at lists.ximian.com; mono-devel-list at lists.ximian.com
> > Subject: Re: [Mono-list] [mono-vb] [Mono-dev] Visual Basic upgrade.
> > 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 the
code unmanageable ?
Miguel, why wasn't this done for gmcs (instead of having to sync mcs
More information about the Mono-devel-list