From: gasche <gasche.dylc@gmail.com>
To: Alain Frisch <alain@frisch.fr>
Cc: Sylvain Le Gall <sylvain@le-gall.net>, caml-list@inria.fr
Subject: Re: [Caml-list] Re: Pre-compiled ocaml binary for windows
Date: Tue, 7 Dec 2010 10:42:56 +0100 [thread overview]
Message-ID: <AANLkTin2aK4+d6CeBuB1j+tHWOD2VTOoiSeDKUnq0wx=@mail.gmail.com> (raw)
In-Reply-To: <4CFDFEA5.3000900@frisch.fr>
[-- Attachment #1: Type: text/plain, Size: 2405 bytes --]
On Tue, Dec 7, 2010 at 10:30 AM, Alain Frisch <alain@frisch.fr> wrote:
> The graphical toplevel does not depend on labltk, so the two issues are
> really unrelated. For crashes with the OCamlWin.exe, I was thinking about
> http://caml.inria.fr/mantis/view.php?id=4399 and
> http://caml.inria.fr/mantis/view.php?id=3052, but this might be pure FUD.
> The real problem is that nobody seems interested enough in this graphical
> toplevel to put serious work on it.
>
I beg to differ. In my experience, the Graphics module is a wonderful tool
to get non-programming beginners interested in OCaml. I have been in the
position of teaching OCaml to beginners, and the single thing they remember
and found *fun* was displaying the mandelbrot fractal, and then playing with
different color functions to get fancy results.
I absolutely agree that Graphics is not the most important thing in OCaml,
and would be very happy to have a decent OCaml installer without it, but
still I think in a second time making it work would be well worth it.
I will probably look for ledit (or lwt toplevel) which seems a better
>> alternative to emacs (too heavy too install).
>>
>
> If your hope is to make OCaml accessible to beginner hobbyists under
> Windows (I assume this is the primary audience for pre-compiled binaries),
> you might still want to provide easy ways to use code editors. Providing
> easy access only to the toplevel (be it graphical, or with a line-editor)
> might be a turnoff for beginners.
In most French "classes préparatoires", students learn programming by --
after a quick exposure to Maple, to be sure they don't risk learning too
much functional programming -- typing code directly in the toplevel.
Advanced software engineering there means "writing code in a notepad so that
the work isn't lost when the toplevel crashes". But it's not directly
relevant, as they still use Caml Light.
I agree that an Emacs integration would be useful, but maybe it could also
provide an ocaml-mode for one of the simpler, less powerful editors with
syntax highlighting and a shortcut to call the compiler. In GNU/Linux land,
those would be Gedit and Kate; I'm not sure what Windows people use now.
(There was also a discussion of Eclipse plugin, but I suspect this isn't
ready and would be a lot of work, so it's probably better to separate the
two efforts)
[-- Attachment #2: Type: text/html, Size: 3627 bytes --]
next prev parent reply other threads:[~2010-12-07 9:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 20:06 José Romildo Malaquias
2010-12-06 15:28 ` [Caml-list] " Damien Doligez
2010-12-06 16:08 ` Sylvain Le Gall
2010-12-06 17:50 ` [Caml-list] " Matthieu Dubuget
2010-12-07 0:24 ` Sylvain Le Gall
2010-12-07 8:21 ` [Caml-list] " Alain Frisch
2010-12-07 9:03 ` Sylvain Le Gall
2010-12-07 9:30 ` [Caml-list] " Alain Frisch
2010-12-07 9:42 ` Sylvain Le Gall
2010-12-07 9:49 ` [Caml-list] " Alain Frisch
2010-12-09 11:54 ` Mauricio Fernandez
2010-12-09 13:12 ` Alain Frisch
2010-12-07 9:42 ` gasche [this message]
2010-12-07 9:52 ` Alain Frisch
2010-12-07 10:29 ` gasche
2010-12-07 15:57 ` [Caml-list] " ygrek
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='AANLkTin2aK4+d6CeBuB1j+tHWOD2VTOoiSeDKUnq0wx=@mail.gmail.com' \
--to=gasche.dylc@gmail.com \
--cc=alain@frisch.fr \
--cc=caml-list@inria.fr \
--cc=sylvain@le-gall.net \
/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