Don Syme: Introduction to F#, Part 2 | Charles

Chadk
excuse me - do you has a flavor?

Wow, bloody hell. My eyes Perplexed

That is SO confusing.

Jake83

The F# console window in Visual Studio looks great. The code snippets at the start helped a lot. But the interactive simulation around the 18 minute mark was what really surprised me.

TommyCarlier
I want my scalps!

Great video. Nice combination of interview and demo.

andrzej
XNA Rocks!!!!

awesome!!! the directx script is fascinating. where can i get it?

coonsta

The DirectX donuts demo is available on The HubFS--the F# community site: http://cs.hubfs.net/forums/thread/95.aspx

coonsta

ChadK: Which part is confusing? Let's break it down!

Chadk
excuse me - do you has a flavor?

coonsta wrote:

ChadK: Which part is confusing? Let's break it down!

I think that the start, moved too fast on. Really, the code seemed nonsense to me.

The Part 1, with the hello world seemed fine. No ;, i like!

The way you select things you want to run 6 minuts into the vidoe is quite cool, for debugging purposes, and in the case its used, where you show what impact each cal do.

What is the language aimed for? Scripting? Or is is supposed to be an anlternative to C#?

The lamda stuff with the events seemed cool. YET i think, like in some of the other stuff, just seemed comfusing, with all the strange characters that is use, like in the line containing the event with the lambda stuff, where did the "_" come from?

I think it was confusing for me, because theres so many characters like -, >, <, _ all over the place. In C#, to compare it with a language i know good, have an acceptable amount of that.

Part 4 seemed even more confusing.

Berre

ChadK: assuming they use the same syntax as ML, the "_" just means ignore this argument.

for example in:
renderer.DrawScene.Add(fun _ -> bla bla...

renderer.DrawScene.Add takes a function as an argument, which itself takes an argument. So they pass an anonymus function, but since this function won't use it's argument, they don't give it a name.. just a _.

It is supposed to help with clearity when reading the code. had they written "fun x -> bla bla..." you might think, "what's this x? it doesn't seem to get used". Instead you put a "_" indicating that you are only accepting an argument to appease the type checker.

Berre

Does the .net CLR support proper tail calls?
I believe that was a problem for som developers, who were working on a ML compiler for the Java VM.