[Mono-devel-list] Re: Mono has been noticed...
normri at samc.com
Fri Jul 2 14:14:35 EDT 2004
I am sure everyone knew this already, but I thought this was sort of
enlightening... This is an exchange on the F# group. So it appears that
Mono 1.0 is being used at least to verify compatibility.
You should not need to recompile programs when moving to new versions
the .NET Framework. However as you know F# has its own binary writer,
and it is possible that the binaries being written are not correct in
some minor detail that means they are not operating correctly on later
versions. I'll try a few examples myself, but please feel free to
any binaries that are no longer functioning correctly.
I regularly recompile code with F# on v2.0 runtimes and haven't seen
problems. Were the binaries compiled with any exotic switches like
BTW recently I've been setting up a testing framework to make sure
F# and Abstract IL compile and work correctly on v1.0, v1.1, v2.0 and
Rotor v1.0, and hopefully Mono 1.0 as well.
From: bounce-fsharp-6488 at list.research.microsoft.com
[mailto:bounce-fsharp-6488 at list.research.microsoft.com] On Behalf Of
Sent: 02 July 2004 18:14
To: F# List
Subject: Re: F# broken on CLR v2.0.40607?
> I installed the latest public Framework SDK and redistributable
> (v2.0.40607, available with these 'Express' products ) and F#
> programs seem broken... They crash with a unhandled (native)
> exception. The same programs run fine on 1.1 (and did run fine on
> previous 2.0s.) Does anyone have any insight?
> Dominic Cooney
>  http://msdn.microsoft.com/express
May be you have to compile your programs again. I had the same problem
from 1.0 to 1.1 version of the framework. Try and let us know.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list