From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Cc: David Teller <David.Teller@ens-lyon.org>
Subject: Re: [Caml-list] Teaching bottomline, part 3: what should improve.
Date: Thu, 24 May 2007 15:18:42 +0100 [thread overview]
Message-ID: <200705241518.42480.jon@ffconsultancy.com> (raw)
In-Reply-To: <1179951657.6097.16.camel@Blefuscu>
On Wednesday 23 May 2007 21:20:57 David Teller wrote:
> On Wed, 2007-05-23 at 00:39 +0100, Jon Harrop wrote:
> > Fascinating. Thanks for reporting the information. If I might be so brash
> > as to comment on the problems you had that have already been fixed by F#:
>
> I mentioned F# to them, by the way. Somewhere along the lines of "It looks
> good, it might be the future, unfortunately, at the moment, you need
> Windows and 400€ worth of Visual Studio to try it".
This blog entry implies that F# works with free editions of Visual Studio:
http://grammerjack.spaces.live.com/blog/cns!F2629C772A178A7C!156.entry
I'll try F# on a machine without the commercial Visual Studio ASAP and see if
I can get it working.
> So far, I have no budget, and Windows.
Could they boot the machines into Linux at the start of each lecture?
> Can I get this graphical throwback without VS ?
I do not believe so although there are some free IDEs:
http://sourceforge.net/projects/sharpedit/
> Div and mod ? How so ?
Div and mod by constants are not optimized by the OCaml compiler, which can
lead to pathological performance on some programs (e.g. sieve, sudoku).
> Plus I tend to believe that the OCaml-style future looks more like
> JoCaml (or Acute, or Oz, or Erlang) than like semaphores.
Except for Erlang, none of those languages have a significant number of users
today. I haven't tried Erlang but it may be worth a look.
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
The F#.NET Journal
http://www.ffconsultancy.com/products/fsharp_journal/?e
next prev parent reply other threads:[~2007-05-24 14:24 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 22:10 David Teller
2007-05-22 22:22 ` [Caml-list] " William D. Neumann
2007-05-23 13:07 ` David Teller
2007-05-22 22:26 ` Erik de Castro Lopo
2007-05-22 23:16 ` skaller
2007-05-23 2:46 ` David Thomas
2007-05-23 9:19 ` Vincent Hanquez
2007-05-23 12:49 ` Brian Hurt
2007-05-23 13:36 ` Gerd Stolpmann
2007-05-23 14:06 ` skaller
2007-05-23 14:54 ` Florian Hars
2007-05-23 15:11 ` Brian Hurt
2007-05-23 21:48 ` Vincent Hanquez
2007-05-24 8:04 ` Markus E.L.
2007-05-24 8:32 ` Vincent Hanquez
2007-05-24 9:51 ` skaller
2007-05-24 11:22 ` Vincent Hanquez
2007-05-23 13:55 ` David Teller
2007-05-22 23:19 ` skaller
2007-05-23 10:41 ` Richard Jones
2007-05-23 13:04 ` David Teller
2007-05-24 13:51 ` Richard Jones
2007-05-24 14:00 ` Robert Fischer
2007-05-24 14:00 ` Jon Harrop
2007-05-24 14:20 ` Robert Fischer
2007-05-24 14:34 ` David Teller
2007-05-24 14:21 ` skaller
2007-05-22 23:39 ` Jon Harrop
2007-05-23 18:54 ` Richard Jones
2007-05-23 19:27 ` Robert C Fischer
2007-05-23 19:34 ` Brian Hurt
2007-05-23 19:54 ` Robert Fischer
2007-05-23 21:46 ` Jon Harrop
2007-05-23 22:14 ` Jacques Garrigue
2007-05-24 1:38 ` Revolution Jon Harrop
2007-05-24 2:40 ` [Caml-list] Revolution skaller
2007-05-24 3:21 ` Chris King
2007-05-24 14:24 ` David Teller
2007-05-24 13:40 ` [Caml-list] Teaching bottomline, part 3: what should improve Brian Hurt
2007-05-23 19:29 ` Jon Harrop
2007-05-23 20:20 ` David Teller
2007-05-24 14:18 ` Jon Harrop [this message]
2007-05-24 14:23 ` skaller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200705241518.42480.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--cc=David.Teller@ens-lyon.org \
--cc=caml-list@yquem.inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).