1. >> Is the correct behaviour of the interractive shell to display the pasted text?

No. I must have got confused here. After watching the Don Syme and Jon Harrop web casts, I've seen that the interractive shell doesn't display the pasted text.

2. >> Is there a keystroke for switching between the VS editor, and the interractive shell?

Silly me. That's a VS issue, not F#. Use Alt-F7 to display a menu of windows, and use Tools->Customize to bind keystrokes to the various ToolWindow commands.

3. >> Is this the preferred way of working in F#, ie. editor and shell, or do people prefer edit/compile/execute?

Still not sure about this. The interractive shell seems to be great for demos, and learning the language, but I have a feeling that when I get into serious programming I'll be mostly sticking within the edit/build/execute environment. Maybe it's just a personal preference thing.

By on 6/30/2007 7:29 PM ()

I use the interactive shell/VS connection extensively. The immediate satisfaction is hard to beat. The only downside, is that when you change some function, you need to remember to "rebuild" everything manually, or your change will not be noticed by the functions which call it. (because unlike Ruby your variables/functions aren't mutable for the most part)

By on 7/1/2007 8:33 AM ()

The current F# Interactive behaviour in this respect is a tradeoff between implementation complexity and functionality.

My vision for a "product" version of F# Interactive would be to support an edit & continue mode that allowed you to replace a function definition, or at least gave you feedback in your script/source window about which definitions were correctly and consistently established. But yes, for the moment, you must reesetablish definitions yourself.

Kind regards

Don

By on 7/1/2007 9:05 AM ()

>> Is there a keystroke for switching between the VS editor, and the interractive shell?

Ctrl-TAB in VS 2005 is also pretty effective. Using the arrow keys can get you to the tool windows.

>> Is this the preferred way of working in F#, ie. editor and shell, or do people prefer edit/compile/execute?

This depends a lot on what you're doing. If you're working and prototyping algorithms that operate primarily against external data sources (e.g. databases or files) then working in FSI is an extremely effective way of prototyping. Likewise if you're using an interactive charting library. However final applications are invariably packaged using the command line compiler (though I know a few groups who package up their code as .fsx scripts)

By on 7/1/2007 2:15 AM ()
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper