caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Brighten Godfrey <pbg@cs.berkeley.edu>
To: Andrej.Bauer@andrej.com
Cc: Caml <caml-list@inria.fr>
Subject: Re: [Caml-list] Teaching ocaml programming
Date: Fri, 26 Sep 2008 05:10:51 -0700	[thread overview]
Message-ID: <23DFDBA7-C437-44E7-8495-D35F396A3889@cs.berkeley.edu> (raw)
In-Reply-To: <48DCC7B8.4070700@fmf.uni-lj.si>

Depending on how flexible you are, nedit + shell might be a workable  
choice.  It is a clean, intuitive, but sufficiently powerful editor.   
Emacs always left me annoyed.

I use, on a daily basis, a small script which acts as a front-end to  
`make' and automatically points you to the error in the code in  
nedit, highlighting the characters that the ocaml compiler complains  
about.  It uses the existing nedit window if you have the file open  
already, or else opens it for you.  The script also works with gcc  
instead of ocaml, and (though I can't vouch for it much) gvim instead  
of nedit.  So my typical development environment consists of nedit  
and a shell in which I compile via the script.

If anyone is interested, I'd be happy to share this.

I guess the main question would be integrating the toplevel with  
nedit.  I imagine there are a number of ways to do this, depending on  
your needs.  You might be able to put something together using  
nedit's scripting language, or just do something entirely external to  
the editor.

~Brighten

On Sep 26, 2008, at 4:30 AM, Andrej Bauer wrote:

> Once again I am teaching a course on theory of programming  
> languages in which we will use ocaml to implement mini-languages.  
> And once again I face the question: which programming environment  
> should we use?
>
> I have so far tried to use (under Windows)
> 1. cygwin + ocaml + XEmacs
> 2. Eclipse + OcaIDE
>
> The second solution worked better than the first, for the simple  
> reason that XEmacs is a complete mystery to students. They really,  
> really hate it. But even with the second soltion we had a lot of  
> trouble, because Eclipse is really complicated, and OcaIDE is sort  
> of experimental and not so good under Windows, so the whole setup  
> was confusing and fragile.
>
> The requirements are very simple:
> 1. easy access to toplevel (with line-editing)
> 2. editor which can send stuff to toplevel, points to errors in  
> source code, and is not Emacs.
>
> Any ideas what to do? We have dual-boot machines (Windows + Ubuntu).
>
> Best regards,
>
> Andrej


  parent reply	other threads:[~2008-09-26 12:10 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-26 11:30 Andrej Bauer
2008-09-26 11:44 ` [Caml-list] " Lukasz Stafiniak
2008-09-26 11:52   ` Andrej Bauer
2008-09-26 12:07     ` Andrej Bauer
2008-09-26 14:31     ` Richard Jones
2008-09-26 14:49       ` Peng Zang
2008-09-26 12:10 ` Brighten Godfrey [this message]
2008-09-26 12:41   ` Andrej Bauer
2008-09-26 12:55     ` Mehdi Dogguy
2008-09-26 17:44     ` Yaron Minsky
2008-09-26 18:59       ` Andrej Bauer
2008-09-26 19:23         ` Hezekiah M. Carty
2008-09-26 20:46     ` David Teller
2008-10-09 21:36     ` Kuba Ober
2008-09-26 22:09   ` Nathaniel Gray
2008-09-26 13:11 ` Hugo Ferreira
2008-09-26 13:33   ` Andrej Bauer
2008-09-26 13:43     ` Hugo Ferreira
2008-09-26 16:15     ` Arthur Chan
2008-09-26 16:52       ` Richard Jones
2008-09-26 22:16         ` Erik de Castro Lopo
2008-09-27  9:44         ` OCaml support on Ubuntu David MENTRE
2008-09-27  9:55           ` [Caml-list] " Erik de Castro Lopo
2008-09-27 11:21           ` Stefano Zacchiroli
2008-09-27 12:17             ` David MENTRE
2008-09-26 16:55       ` [Caml-list] Teaching ocaml programming Andrej Bauer
2008-09-26 17:11       ` Stefano Zacchiroli
2008-09-26 18:16         ` Hugo Ferreira
2008-09-26 22:20         ` Erik de Castro Lopo
2008-09-26 22:08       ` Erik de Castro Lopo
2008-09-27  6:15         ` Vu Ngoc San
2008-09-27  9:22         ` Stefano Zacchiroli
2008-09-27  9:33           ` Erik de Castro Lopo
2008-09-27  9:36             ` Erik de Castro Lopo
2008-09-27 11:16             ` Stefano Zacchiroli
2008-09-26 14:29 ` Peng Zang
2008-09-26 15:18 ` Dario Teixeira
2008-09-26 16:17   ` Andrej Bauer
2008-09-26 16:55     ` Richard Jones
2008-09-26 17:01     ` Peng Zang
2008-09-28  0:06       ` Brighten Godfrey
2008-09-26 20:30 ` David Teller
2008-09-26 22:05 ` Nathaniel Gray
2008-10-09 21:41 ` Kuba Ober
2008-10-10 17:08   ` Andrej Bauer
2008-10-11 15:58     ` Kuba Ober
2008-10-11 16:19       ` Kuba Ober
2008-10-11 21:18         ` Andrej Bauer
2008-10-13 23:21           ` Kuba Ober

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=23DFDBA7-C437-44E7-8495-D35F396A3889@cs.berkeley.edu \
    --to=pbg@cs.berkeley.edu \
    --cc=Andrej.Bauer@andrej.com \
    --cc=caml-list@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).