On May 15, 2010, at 5:40 AM, Daryoush Mehrtash wrote:
the speaker talks about F# on .Net platform. Early on in the talk
he says that they did F# because haskell would be "hard to make as
a .Net language".Does anyone know what features of Haskell make
it difficult as .Net language?
La
dmehrtash:
> Would there be issues (lazy evaluation, type system...) with other languages
> calling a Haskell code in a hypothetical Haskell in .NET?
There are always issues, but conceptually it is no harder than calling
Haskell from C, which is relatively straight forward.
__
Would there be issues (lazy evaluation, type system...) with other
languages calling a Haskell code in a hypothetical Haskell in .NET?
Daryoush
On Fri, May 14, 2010 at 10:43 AM, Don Stewart wrote:
> dmehrtash:
> > In this presentation
> >
> >
> http://norfolk.cs.washington.edu/htbin-post/unres
Hello Don,
Friday, May 14, 2010, 9:43:38 PM, you wrote:
> Most .NET libraries are imperative, use mutable state -- so binding to
they are also OOP. ocaml supports OOP while haskell doesn't
--
Best regards,
Bulatmailto:bulat.zigans...@gmail.com
___
dmehrtash:
> In this presentation
>
> http://norfolk.cs.washington.edu/htbin-post/unrestricted/colloq/details.cgi?id=
> 907
>
> the speaker talks about F# on .Net platform. Early on in the talk he says
> that they did F# because haskell would be "hard to make as a .Net language".
>
> Does a
In this presentation
http://norfolk.cs.washington.edu/htbin-post/unrestricted/colloq/details.cgi?id=907
the speaker talks about F# on .Net platform. Early on in the talk he says
that they did F# because haskell would be "hard to make as a .Net
language".Does anyone know what features of Has
