Page 3 of 3 FirstFirst 123
Results 21 to 27 of 27
  1. #21
    Join Date
    Oct 2006
    Posts
    1,548
    Stop moaning you giant ass wimp.
    [quote][\quote]

  2. #22
    Join Date
    Mar 2004
    Posts
    0
    Interesting answer about some questions relating to F#... Written by none other then Eric Lippert (one of the senior developers on the C# compiler team):

    http://stackoverflow.com/questions/2...170753#2170753

    Also,
    http://stackoverflow.com/questions/2...835936#2835936
    http://stackoverflow.com/questions/2...704795#2704795

    And:
    http://blogs.msdn.com/b/wesdyer/arch...of-monads.aspx

  3. #23
    Join Date
    Nov 2008
    Location
    41° 28′ 56″ N, 81° 40′ 11″ W
    Posts
    2,399
    You're right, Nelson, that is interesting...who knew that F# would be destined to be more popular than the almighty C# in terms of .Net-based languages? I always thought that C# was considered the backbone standard to .Net and the new Visual Studio. Seems like I underestimated the F# language. Thanks for this heads-up.
    PC Specs: Antec 900 ATX Case, Gigabyte 790GX Mobo, AMD Phenom II x4 955, Corsair HX620W PSU, Corsair Vengeance 16GB (4x4GB) DDR3-1600, EVGA GTX 680 2GB GDDR5, 3D Vision Kit 2, LG 8x Blu-ray Burner, Intel X25-M SSD, 500GB+640GB WD Caviar Blacks, Win 7 Pro x64, DAS Pro K/B, MX518 Mouse, Logitech Z-2300 Speakers, Toshiba 32TL515U 32" 3DTV, Wacom Bamboo Fun Large Tablet.

  4. #24
    Join Date
    Aug 2005
    Location
    mantragora
    Posts
    763
    But, but, but there is no IntelliSence for F# in VS ! How could it be ?

  5. #25
    Join Date
    Nov 2008
    Location
    41° 28′ 56″ N, 81° 40′ 11″ W
    Posts
    2,399
    That brings up a very good point, Swann. I was always a big fan of IntelliSense from day one since that was brought into Visual Studio. It's always saved me a TON of trouble. I'm hoping that in future generations of F# that Microsoft will be able to make it so IntelliSense will make overall coding experiences even easier in the long run. Certainly did me wonders since VS 6.0, I believe was one of the first versions that actually used this, but since .NET, that has become a standard tool for more efficient coding throughout.

    EDIT: Oh yeah, and F# doesn't support ReSharper that I know of, that's another point that Nelson should have made. I believe as of the current generation of the ReSharper Tool, it can only support C# and VB.NET, that I know of. No word if JetBrain is going to bring any support to F# in the near future.
    Last edited by WedgeBob; 12-01-2010 at 03:45 PM.
    PC Specs: Antec 900 ATX Case, Gigabyte 790GX Mobo, AMD Phenom II x4 955, Corsair HX620W PSU, Corsair Vengeance 16GB (4x4GB) DDR3-1600, EVGA GTX 680 2GB GDDR5, 3D Vision Kit 2, LG 8x Blu-ray Burner, Intel X25-M SSD, 500GB+640GB WD Caviar Blacks, Win 7 Pro x64, DAS Pro K/B, MX518 Mouse, Logitech Z-2300 Speakers, Toshiba 32TL515U 32" 3DTV, Wacom Bamboo Fun Large Tablet.

  6. #26
    Join Date
    Nov 2008
    Location
    41° 28′ 56″ N, 81° 40′ 11″ W
    Posts
    2,399
    OMG, I'm an idiot for not bringing this up when Nelso was asking for suggestions for "Nelson's Corner" videos...

    I thought for sure that Nelson was going to do a whole miniseries of VTMs catered towards introductions to F# and teaching us the ins and outs of the language. I mean, I don't think there have been any VTMs made for F# yet, and this would bring a nice change of pace over all the C# and C++ VTMs that we all have. I'd have to think that Nelson would probably be all for a VTM Series on this topic.
    PC Specs: Antec 900 ATX Case, Gigabyte 790GX Mobo, AMD Phenom II x4 955, Corsair HX620W PSU, Corsair Vengeance 16GB (4x4GB) DDR3-1600, EVGA GTX 680 2GB GDDR5, 3D Vision Kit 2, LG 8x Blu-ray Burner, Intel X25-M SSD, 500GB+640GB WD Caviar Blacks, Win 7 Pro x64, DAS Pro K/B, MX518 Mouse, Logitech Z-2300 Speakers, Toshiba 32TL515U 32" 3DTV, Wacom Bamboo Fun Large Tablet.

  7. #27
    Join Date
    Jul 2008
    Location
    Portsmouth, England
    Posts
    436
    Quote Originally Posted by swann View Post
    But, but, but there is no IntelliSence for F# in VS ! How could it be ?
    There is when it can determine the type of the identifier or expression under the cursor. But with all the type inference in F#, often times a variable has no fixed type as you are writing a line of code. Type inference in a massive benefit because it makes it far easier to write generic code than in C#, but with the Intellisense issue it could also a disadvantage I guess. Thing is you can still declare the type of a parameter in an F# function (and sometimes you need to), but in general I'll stick to typing less. The Error List window is very informative and updates in real time to help you catch mistakes.

Page 3 of 3 FirstFirst 123

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •