OCalDE

OCalDE

[Christophe Raffalli]

Dear list members,

Here is a list of questions I have about eclipse and OCalDE (some of them probably easy,
because I am not used to eclipse):

- How can I tell eclipse parser about my own camlp4 extension ?

- How can I configure some "Run script" (typically a "make check" launched from eclipse), to test
and debug my code ?

- I find that "format using camlp4" adds to much parenthesis, is it possible to do something about 
it (it is probably necessary to fine tune the camlp4 pretty printer ?)

- The "Content Assist" menu is very nice ... but even with the proper folder added to the Project 
Path, It does not always work for my own local function (this may be related to my next question)

- I use unison ... I told it not to synchronise ~/.eclipse and ~/worspace/.metadata, but this does 
not work well enough (If I create a project on another machine, the new project needs to be added on 
the other machine despite the fact that the folder was copied by unison in the workspace folder). So 
what is the correct way to use unison together with eclipse (I am afraid to make a mess in eclipse 
files) ? (remark I do not quit always eclipse before synchronisation with unison)

- No progress about the darcs incompatibility related to "linked URLs" used by OCaIDE and not 
supported by darcs eclipse.

- I had two or three time a file opened where all modifications where in fact not performed on the 
filesystem (closing and reopening the file solved the problem). Is this a known bug with eclipse (I 
can not reproduce it yet) ?

Cheers,
-- 
Christophe Raffalli
Université de Savoie
Batiment Le Chablais, bureau 21
73376 Le Bourget-du-Lac Cedex

tél: (33) 4 79 75 81 03
fax: (33) 4 79 75 87 42
mail: Christophe.Raffalli@univ-savoie.fr
www: http://www.lama.univ-savoie.fr/~RAFFALLI

Re: [Caml-list] OCalDE

[Nicolas Bros]

> How can I tell eclipse parser about my own camlp4 extension ?

For now, you can't. OcaIDE uses a custom parser written in Java,
copied from the rules of the original Ocaml parser. So, it only parses
standard syntax.
To parse a modified syntax, the file would first have to be processed
by camlp4.
But then, how would OcaIDE get the positions of the elements in the
original unprocessed file?

> How can I configure some "Run script" (typically a "make check" launched from
> eclipse), to test and debug my code ?

Custom makefile targets will be supported in a future version.

> I find that "format using camlp4" adds to much parenthesis, is it possible to do
> something about it (it is probably necessary to fine tune the camlp4 pretty printer ?)

I think you know a lot more about camlp4 than I, so I guess you're right.

> what is the correct way to use unison together with eclipse

I don't use unison, so I can't help you.

> No progress about the darcs incompatibility related to "linked URLs" used by OCaIDE
> and not supported by darcs eclipse.

I think this is more of a problem with darcs than with OcaIDE.


> I had two or three time a file opened where all modifications where in fact not
> performed on the filesystem (closing and reopening the file solved the problem).
> Is this a known bug with eclipse (I can not reproduce it yet) ?

Usually, this happens the other way around: the Eclipse workspace does
not reflect changes on the file system until you refresh your
workspace in Eclipse.

Re: [Caml-list] OCalDE

[Christophe Raffalli]

Nicolas Bros a écrit :
>> How can I tell eclipse parser about my own camlp4 extension ?
>
> For now, you can't. OcaIDE uses a custom parser written in Java,
> copied from the rules of the original Ocaml parser. So, it only parses
> standard syntax.
> To parse a modified syntax, the file would first have to be processed
> by camlp4.
> But then, how would OcaIDE get the positions of the elements in the
> original unprocessed file?
>
>
You could take the same approach than proof general for eclipse, writte 
a parser with anything (this includes camlp4)
whose output is a copy of the original file with xml annotation. Such a 
parser should allow camlp4 extension ...

The main problem, is that appart from the xml annotation the text should 
not be changed, so a camlp4 pretty-printer will not workd. However, the 
parser could simply produce the position where to add xml annotation 
that are inserter in a second phase into the original
input ...

So what needs to be written is a camlp4 parser that produce pairs with 
positions and xml annotation ... and that also perform a little error 
recovery ...
>> No progress about the darcs incompatibility related to "linked URLs" 
>> used by OCaIDE
>> and not supported by darcs eclipse.
>
> I think this is more of a problem with darcs than with OcaIDE.
>
Yes, probably, but what is a "linked URL" and what is their use in 
OCaIDE ? If it is the link to the ocaml library, then
it is strange that darcs think linked URL matters ?

Re: [Caml-list] OCalDE

[Alain Frisch]

Nicolas Bros wrote:
>> How can I tell eclipse parser about my own camlp4 extension ?
> 
> For now, you can't. OcaIDE uses a custom parser written in Java,
> copied from the rules of the original Ocaml parser. So, it only parses
> standard syntax.
> To parse a modified syntax, the file would first have to be processed
> by camlp4.
> But then, how would OcaIDE get the positions of the elements in the
> original unprocessed file?

Camlp4 makes this information available when it dumps a binary version 
of the Caml AST. If the problem is to read this marshaled value, it 
should not be too difficult to write another printer for Camlp4 (e.g. 
xml-ish, json-ish or lisp-ish, dependening on what is easier to parse in 
OcaIDE).


-- Alain

Re: [Caml-list] OCalDE

[Nicolas Bros]

> Camlp4 makes this information available when it dumps a binary version
> of the Caml AST. If the problem is to read this marshaled value, it
> should not be too difficult to write another printer for Camlp4 (e.g.
> xml-ish, json-ish or lisp-ish, dependening on what is easier to parse in
> OcaIDE).

That is a good idea, but how do you write a camlp4 printer? I have
never used camlp4, and I couldn't find documentation on this point.

Re: [Caml-list] OCalDE

[Jon Harrop]

On Wednesday 25 July 2007 08:27:58 Nicolas Bros wrote:
> For now, you can't. OcaIDE uses a custom parser written in Java,
> ...

I was wondering how the Eclipse plug-in was written given that the underlying 
infrastructure is written in Java. Would it not be much easier to develop an 
IDE in OCaml using something like LablGTK?

-- 
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
OCaml for Scientists
http://www.ffconsultancy.com/products/ocaml_for_scientists/?e

Re: [Caml-list] OCalDE

[Nicolas Bros]

> How can I configure some "Run script" (typically a "make check" launched from
> eclipse), to test and debug my code ?

I just remembered this:
You can use the "External tools" in Eclipse in "Run > External Tools >
Open External Tools Dialog...". Here, you can create a program launch
configuration, define what executable to launch ("make"), in which
directory to start it ("${project_loc}"), and give it "check" as
argument to follow your example. You can also add it as a favorite to
access it faster.

Then, you will be able to start it by clicking on the "External tools"
button on the tools bar.

Re : [Caml-list] OCalDE

[Matthieu Wipliez]

[-- Attachment #1: Type: text/plain, Size: 1736 bytes --]

In my experience (development of a plug-in using the GEF framework),
Eclipse plug-ins are written in Java. However, nothing prevents you to write it in another language that allows C bindings, and make it available as a shared library (.so or .dll); calling functions is then done using JNI (Java - C bindings). Which is possible with OCaml since it allows callbacks from C.

As for developing an IDE from scratch rather than use Eclipse, being given the number of features provided by Eclipse, IMHO it is not only like reinventing the wheel, but more like reinventing the car itself...

----- Message d'origine ----
De : Jon Harrop <jon@ffconsultancy.com>
À : caml-list@yquem.inria.fr
Envoyé le : Mercredi, 25 Juillet 2007, 11h33mn 53s
Objet : Re: [Caml-list] OCalDE

On Wednesday 25 July 2007 08:27:58 Nicolas Bros wrote:
> For now, you can't. OcaIDE uses a custom parser written in Java,
> ...

I was wondering how the Eclipse plug-in was written given that the underlying 
infrastructure is written in Java. Would it not be much easier to develop an 
IDE in OCaml using something like LablGTK?

-- 
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
OCaml for Scientists
http://www.ffconsultancy.com/products/ocaml_for_scientists/?e

_______________________________________________
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







      _____________________________________________________________________________ 
Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail 

[-- Attachment #2: Type: text/html, Size: 2522 bytes --]

Re: [Caml-list] OCalDE

[Jon Harrop]

On Wednesday 25 July 2007 13:30:12 Matthieu Wipliez wrote:
> As for developing an IDE from scratch rather than use Eclipse, being given
> the number of features provided by Eclipse,

What exactly does Eclipse provide for IDE developers?

> IMHO it is not only like reinventing the wheel, but more like reinventing
> the car itself... 

And what is rewriting camlp4 in Java like?

-- 
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
OCaml for Scientists
http://www.ffconsultancy.com/products/ocaml_for_scientists/?e

Re: [Caml-list] OCalDE

[Nicolas Bros]

> What exactly does Eclipse provide for IDE developers?

Eclipse provides a gigantic framework for application and plug-in developers.
A lot of features come for free, like:
- Text editors, which support syntax-coloring (with content
partitioning), completion, hyperlinks, code folding, hooking up with
an outline, ...
- Local history, which allow you to restore a previous version of a file
- Content versioning system
- Views, which can be moved, minimized, closed, restored, ...
- A building framework
- A debugging framework
- Progress monitors (which show a progress indicator and allow
interrupting the task)
- Perspectives (a way of organizing views by tasks)
- Preferences, which are automatically saved and restored
- Property pages
- Wizards, for creating new projects, etc.
The list goes on and on...

> And what is rewriting camlp4 in Java like?

There is no need to, camlp4 (like any other command-line tool) can be
called from Eclipse, and its output used in OcaIDE.