caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Hugo Ferreira <hmf@inescporto.pt>
To: Alain Frisch <alain@frisch.fr>
Cc: Jon Harrop <jon@ffconsultancy.com>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Favorite OCaml editor?
Date: Tue, 05 Jan 2010 14:14:31 +0000	[thread overview]
Message-ID: <4B434947.6060406@inescporto.pt> (raw)
In-Reply-To: <4B4313FB.6070808@frisch.fr>


To the OP:

Eclipse + OcalIDE

Alain Frisch wrote:
> On 05/01/2010 09:13, Jon Harrop wrote:
>> I think the best way to write a decent editor for OCaml would be to 
>> write one
>> using LablGTK for the GUI and camlp4 to parse OCaml code.
> 
> It is indeed very tempting to reuse an existing OCaml parser in order to 
> support syntax-related features (indentation, coloring, and whatnot); 
> especially if you can then support syntax extension properly.
> 
> The problem is that the editor is supposed to work even with partial or 
> syntactically invalid code, which is not the case for the OCaml parsers 
> (built-in or Camlp4-based). It would be great to have a parser for OCaml 
> syntax, with robust error recovery. Has anyone worked on such a project?
> 
> 

This is indeed a thorny issue. The developer of OcalIDE is taking
another stab at this but this time using Camlp4 [1].

BTW the way the Haskell eclipse plug-in [2] also has to deal with such
issues. In their case they use a generic library and API [3] that should
be usable by any number of IDEs and editors (already used by emacs). May
be of interest to you also.

[1] http://ocaml.eclipse.free.fr/forum/viewtopic.php?f=1&t=226
[2] http://eclipsefp.sourceforge.net/
[3] http://code.google.com/p/scion-lib/


Hugo F.


> Alain
> 
> 
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
> 


  parent reply	other threads:[~2010-01-05 14:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05  6:03 Grant Rettke
2010-01-05  6:08 ` [Caml-list] " Mihamina Rakotomandimby
2010-01-05  6:22 ` Mike Lin
2010-01-05  6:36   ` Alexander Voinov
2010-01-05  7:01   ` Erik de Castro Lopo
2010-01-05  7:31 ` Daniel Bünzli
2010-01-05 11:28   ` Jon Harrop
2010-01-05 16:55     ` Laurent Le Brun
2010-01-05  8:13 ` Jon Harrop
2010-01-05 10:27   ` Alain Frisch
2010-01-05 10:44     ` Nicolas Pouillard
2010-01-05 13:00       ` Alain Frisch
2010-01-05 13:11         ` Nicolas Pouillard
2010-01-05 14:14     ` Hugo Ferreira [this message]
2010-01-05  8:45 ` Maxence Guesdon
2010-01-05 11:23   ` Jon Harrop
2010-01-05 10:50     ` Maxence Guesdon
2010-01-05 10:24 ` Vincent Aravantinos
2010-01-05 11:02   ` Richard Jones
2010-01-05 10:58 ` Richard Jones
2010-01-05 12:21 ` Florent Ouchet
2010-01-05 17:32   ` Tim Hanson
2010-01-05 13:09 ` Martin DeMello
2010-01-05  6:21 Gaius Hammond

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=4B434947.6060406@inescporto.pt \
    --to=hmf@inescporto.pt \
    --cc=alain@frisch.fr \
    --cc=caml-list@yquem.inria.fr \
    --cc=jon@ffconsultancy.com \
    /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).