<br><br><div><span class="gmail_quote">On 8/29/07, <b class="gmail_sendername">Joel Reymont</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I don't believe the parsing of the Erlang code in these two is done<br>in Erlang. Distel is surely using Emacs Lisp and ErlIDE must be using<br>Java.<br><br></blockquote></div>Actually, Erlide is using Erlang. Why write a scanner and aparser from scratch when we have perfectly good tools at our disposal?
<br><br>We are trying to move as much as possible of the functionality to the Erlang side, leaving Java just as thin wrappers, possibly with some caching if necessary. This is harder than it sounds, because Eclipse is so complex.
<br>To this reason I implemented a way to call Java code from Erlang, so that for example we can pass a progress monitor to a lengthy operation and have it called from the Erlang code.<br><br>The biggest problem we have is the impedance mismatch between the natural concurrency of an Erlang system and the relatively contrived use of threading in a Java application with a GUI.