AW: [mono-vb] Just a small bit of information...
Fri, 24 Sep 2004 10:03:37 +0200
Hi Rob, hi Jambu,
In the past I've discovered some trouble when you use some assemblies =
compiled with MS.NET and you mix them with other assemblies compiled =
That's why I wanted to carfully ask if these optional arguments are =
handles by both worlds in the same way. I only wanted to prevents us =
from developing a solution which works fine as long as you stay in the =
Mono world only.
That's also why I asked for my scenarion with my 1st MS.NET compiled =
assembly which implements some optional values and on the other hand I =
had a 2nd assembly compiled with mbas which should use the first one.
Maybe, I'm too carfull, now ;-)
Sorry for the noise...
Von: Rob.Tillie@Student.tUL.EDU [mailto:Rob.Tillie@Student.tUL.EDU]=20
Gesendet: Mittwoch, 22. September 2004 20:41
An: Jochen Wezel; firstname.lastname@example.org; email@example.com
Betreff: RE: [mono-vb] Just a small bit of information...
As I understand this, that scenario won't work because mbas has to =
'post-process' that attribute.
But isn't that a neglectable scenario? If we can, we should avoid the =
huge task of rewriting the namespace, certainly before the 1.2 release.
> -----Original Message-----
> From: Jochen Wezel [mailto:firstname.lastname@example.org]
> Sent: Wednesday, September 22, 2004 12:41 PM
> To: B Anirban; email@example.com
> Subject: AW: [mono-vb] Just a small bit of information...
> > So, we took a round about way to fix the problem
> > - A new internal attribute __DefaultArgumentValue is introduced in=20
> > Microsoft.VisualBasic.CompilerServices namespace.
> Will it be compatible with MS.NET at the end? Let's say we compile an=20
> EXE and the library with our optional value had been compiled with=20
> Mono-vb mailing list