Comments on: C#/F#: Using .NET framework classes http://www.markhneedham.com/blog/2009/06/16/cf-using-net-framework-classes/ Thoughts on Software Development Sat, 11 Feb 2012 23:17:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Mark Needham http://www.markhneedham.com/blog/2009/06/16/cf-using-net-framework-classes/comment-page-1/#comment-18731 Mark Needham Tue, 16 Jun 2009 11:54:20 +0000 http://www.markhneedham.com/blog/?p=1337#comment-18731 I used it once and got told off! Probably should have investigated further as to why it's not considered a good idea. I'm thinking it would be around the fact that it's not obvious that the result would be put into a parameter although I guess you could equally argue that's what the out parameter is there to describe. I used it once and got told off! Probably should have investigated further as to why it’s not considered a good idea.

I’m thinking it would be around the fact that it’s not obvious that the result would be put into a parameter although I guess you could equally argue that’s what the out parameter is there to describe.

]]> By: Tim Robinson http://www.markhneedham.com/blog/2009/06/16/cf-using-net-framework-classes/comment-page-1/#comment-18730 Tim Robinson Tue, 16 Jun 2009 11:43:23 +0000 http://www.markhneedham.com/blog/?p=1337#comment-18730 I don't understand the problem with out parameters. I have a co-worker who says the same thing: that out parameters are frowned upon, so you shouldn't use TryGetValue. Although FxCop complains if you write an out parameter into one of your own methods, the Framework Design Guidelines book advocates this exact TryGetValue pattern. I agree F#'s bool * string approach is neater; it forces you to handle the case when TryGetValue returns false. (Although if TryGetValue had been written in F#, I guess it would have returned Option). I don’t understand the problem with out parameters. I have a co-worker who says the same thing: that out parameters are frowned upon, so you shouldn’t use TryGetValue. Although FxCop complains if you write an out parameter into one of your own methods, the Framework Design Guidelines book advocates this exact TryGetValue pattern.

I agree F#’s bool * string approach is neater; it forces you to handle the case when TryGetValue returns false. (Although if TryGetValue had been written in F#, I guess it would have returned Option).

]]>