Re: [Haskell-cafe] Re: Editors for Haskell

hya this topic is hot, and I wonder why :s well, I've been thinking, the EclipseFP people have done more or less a fine job (I'm trying their "live" build, things feel natural). but the problem is, to build something like EclipseFP you have to know both Java and Haskell and on top of that you have to be very familiar with the Eclipse plug-in architecture. whining: - should have had folds for where and let clauses - the error messages are still cryptic (and unformatted!) - there was no tooltip for functions - the default color chosen for functions is way too bright - ... (many silly Java expectations follow) but what if we _ask_ eclipse.org to help us out? like, an official collaboration? they have done an excellent job promoting free software. this should be sort of a recognition for them. the point is, GUI _is_ easier to build in Java. and those people are experts. should not take much time. as for me, I'll be happy to watch the impact Haskell will have on Java fans. two things just to make sure this post is not absolutely superfluous: - without drinking anything I was feeling drunk that night and so I posted some of my hIDEous thoughts in http://www.haskell.org/haskellwiki/Talk:HIDE page. Lemmih left a note saying I was not so genuine, a project called Proxima has implemented (or at least, proposed) most of the ideas. I checked it out and was ashamed of my lack of original idea. however, though the paper was absolutely dreamy, the implementation,.. how do I put it humbly.. sucked. I am sure the Eclipse people will appreciate the Proxima ideas. please ask them to build a Proxima style IDE for Haskell. - about formatted error messages (I am sure you guys don't care), could someone build a light GHC front end that given a .hs/.lhs file produces two XML files with specified DTD, the parsed structure and the error messages? the reason for choosing XML is that not only the Java people (including Leif Frenzel) but also virtually anyone can access these information (in order to create a great IDE) immediately and without loosing the structure. cheers, Imam __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Hi
- about formatted error messages (I am sure you guys don't care), could someone build a light GHC front end that given a .hs/.lhs file produces two XML files with specified DTD, the parsed structure and the error messages? the reason for choosing XML is that not only the Java people (including Leif Frenzel) but also virtually anyone can access these information (in order to create a great IDE) immediately and without loosing the structure.
This would be great, and could perhaps be used by other compilers as well, but is likely to be a lot of work. Someone will need to go through all possible Haskell error messages, probably assign an ID to each one, and write something about the exact meaning of the error message. However, this would be really really useful for beginners to find more information. I started trying to do this with Yhc, but got bored once I got past 10 error messages. (See http://www-users.cs.york.ac.uk/~malcolm/cgi-bin/darcsweb.cgi?r=yhc-devel;a=h... for my attempt) Thanks Neil

Imam,
On 6/8/06, Imam Tashdid ul Alam
- about formatted error messages (I am sure you guys don't care), could someone build a light GHC front end that given a .hs/.lhs file produces two XML files with specified DTD, the parsed structure and the error messages?
I would really appreciate that. I am the one maintaining EclipseFP now and I know that having the syntax-tree in XML format would help us a lot. For now, we use our own Haskell parser (written in Java). It is not a full parser (and maybe it'll never be), but it allows us to do some tricks like showing a simple code outline and do some code assistance. Maybe this isn't as much work as structuring the error messages. Cheers, Thiago Arrais

GHC already carefully collects up almost all messages in a data type
called Message, so they are easy to re-direct. However at the moment
they collected as strings (well as Pretty.Doc values actually) so they
have lost their structure.
I believe that at one time I had a data type for error messages, but
there are so many of them and they change pretty often that it was quite
a pain having a centralised data type for this. And at the time there
was lots of pain and virtually no gain.
Changing this would be tedious but do-able. If anyone wants to
undertake it, let us know.
Simon
| -----Original Message-----
| From: haskell-cafe-bounces@haskell.org
[mailto:haskell-cafe-bounces@haskell.org] On Behalf Of
| Thiago Arrais
| Sent: 08 June 2006 20:07
| To: haskell-cafe@haskell.org
| Subject: Re: [Haskell-cafe] Re: Editors for Haskell
|
| Imam,
|
| On 6/8/06, Imam Tashdid ul Alam
participants (4)
-
Imam Tashdid ul Alam
-
Neil Mitchell
-
Simon Peyton-Jones
-
Thiago Arrais