caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: Tomasz Jamroszczak <jamrok@gazeta.pl>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] making ocaml mainstream
Date: Sat, 19 Aug 2006 14:34:03 +1000	[thread overview]
Message-ID: <1155962043.28068.40.camel@rosella.wigram> (raw)
In-Reply-To: <op.teibicuojx4fme@xn--led-hdas.ip.pop.e-wro.net.pl>

On Sat, 2006-08-19 at 03:24 +0200, Tomasz Jamroszczak wrote:
>    I've been playing for a second time with Ocaml for a time now and I've  
> got some insights in what could make the language more popular.

IMHO: the lack of debugging support on Windows is an illusion.
Ocaml code just works (TM), you don't need a debugger. A couple
of debugging prints is usually enough to find problems.

I never use debuggers. Debuggers are for assembler geeks
and would-be assembler geeks writing low level C code :)

I think this is a matter of education -- you're looking
for a tool you don't need in the first place.

As to IDE support -- well it is much the same. I'm happy
enough with a text editor and command line compilation
with a script. It is only slightly more painful on Windows
than on Unix.

However I think you're right that a Visual Studio plugin
is the way to go. No one familiar with the VS editor
would ever want to learn a horrendous monstrosity like
Emacs .. let alone Vim's archaic terminal editing concepts
(ducks for cover!)

In an industrial setting, having Ocaml as part of a VS
project would be winner.

-- 
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net


  parent reply	other threads:[~2006-08-19  4:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-19  1:24 Tomasz Jamroszczak
2006-08-19  1:29 ` [Caml-list] " Joel Reymont
2006-08-19  4:34 ` skaller [this message]
2006-08-22 21:21   ` Mike Lin
2006-08-22 23:15     ` Joel Reymont
2006-08-23  0:00       ` Markus Mottl
2006-08-23  8:59         ` Joel Reymont
2006-08-23 10:30           ` Richard Jones
2006-08-23 10:54             ` Anil Madhavapeddy
2006-08-22 20:19 ` Richard Jones

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=1155962043.28068.40.camel@rosella.wigram \
    --to=skaller@users.sourceforge.net \
    --cc=caml-list@inria.fr \
    --cc=jamrok@gazeta.pl \
    /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).