From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.1.3 Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by yquem.inria.fr (Postfix) with ESMTP id 6B813BB84 for ; Fri, 26 Sep 2008 14:10:53 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap8DADJu3EjAXQImiGdsb2JhbACTHwEBARUioWWGVjyBZA X-IronPort-AV: E=Sophos;i="4.33,313,1220220000"; d="scan'208";a="29616716" Received: from discorde.inria.fr ([192.93.2.38]) by mail4-smtp-sop.national.inria.fr with ESMTP; 26 Sep 2008 14:10:52 +0200 Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by discorde.inria.fr (8.13.6/8.13.6) with ESMTP id m8QCAo7O026276 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=OK) for ; Fri, 26 Sep 2008 14:10:52 +0200 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap8DAG5u3Eip5TxXiGdsb2JhbACTHwEBARUioWeGVjyBZA X-IronPort-AV: E=Sophos;i="4.33,313,1220220000"; d="scan'208";a="17378814" Received: from gateway0.eecs.berkeley.edu ([169.229.60.87]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 26 Sep 2008 14:10:50 +0200 Received: from [10.0.1.4] (adsl-70-137-140-236.dsl.snfc21.sbcglobal.net [70.137.140.236]) (authenticated bits=0) by gateway0.EECS.Berkeley.EDU (8.14.3/8.13.5) with ESMTP id m8QCAgjj025089 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 26 Sep 2008 05:10:43 -0700 (PDT) In-Reply-To: <48DCC7B8.4070700@fmf.uni-lj.si> References: <48DCC7B8.4070700@fmf.uni-lj.si> Mime-Version: 1.0 (Apple Message framework v753.1) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <23DFDBA7-C437-44E7-8495-D35F396A3889@cs.berkeley.edu> Cc: Caml Content-Transfer-Encoding: 7bit From: Brighten Godfrey Subject: Re: [Caml-list] Teaching ocaml programming Date: Fri, 26 Sep 2008 05:10:51 -0700 To: Andrej.Bauer@andrej.com X-Mailer: Apple Mail (2.753.1) X-Miltered: at discorde with ID 48DCD14A.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; ocaml:01 nedit:01 emacs:01 nedit:01 ocaml:01 compiler:01 gcc:01 toplevel:01 andrej:01 cygwin:01 toplevel:01 emacs:01 andrej:01 26,:98 ubuntu:98 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