From: Thiago A. <thi...@gm...> - 2005-06-14 14:36:06
|
Hello all, I am willing to start the first prototype for the debugger. The main purpose of this prototype is to learn the eclipse platform, improve our understanding of functional debugging techniches and approaches and evaluate some implementation strategies. What I am willing to do in the prototype is: 1. write a parser in Java for a functional language and integrate it with the plug-in we have to this point. This parser should provide the execution engine (and UI components) with the info needed to trace the execution back and forth (to source code) 2. write a translator that gets a parser output and produces executable code for the execution engine 3. write the execution engine (graph reducer), which should: (a) accept breakpoint definition upon execution startup and during it (i.e. we are not stuck to breakpoint definition before program startup only) (b) be able to interpret all programs written in the chosen language (c) provide an observer interface for components interested on observing the execution 4. write the UI components for showing the execution engine output (i.e. debugger UI components) I will not use a type checker yet. Of course this language will be a very simple one and hopefully a subset of haskell. Provided our objectives, the old Haskell parser written in Java would be a very good starting point. Where can I find it? Upon prototype completion, I will publish a report about its development and the main concerns I may have found. Good luck for us, Thiago Arrais thi...@gm... |
From: Leif F. <hi...@le...> - 2005-06-15 21:04:51
|
Hi Tiago, > I am willing to start the first prototype for the debugger. The main > purpose of this prototype is to learn the eclipse platform, improve > our understanding of functional debugging techniches and approaches > and evaluate some implementation strategies. > > What I am willing to do in the prototype is: > > 1. write a parser in Java for a functional language and integrate it > with the plug-in we have to this point. This parser should provide the > execution engine (and UI components) with the info needed to trace the > execution back and forth (to source code) > > 2. write a translator that gets a parser output and produces > executable code for the execution engine > > 3. write the execution engine (graph reducer), which should: > (a) accept breakpoint definition upon execution startup and during it > (i.e. we are not stuck to breakpoint definition before program startup > only) > (b) be able to interpret all programs written in the chosen language > (c) provide an observer interface for components interested on > observing the execution > > 4. write the UI components for showing the execution engine output > (i.e. debugger UI components) Great :-) This sounds like a bit of a programme. Since most of this is not my area of expertise, I'm very probably not able to contribute here, except maybe in 4), so just let me know if I can do anything in that field. > I will not use a type checker yet. Of course this language will be a > very simple one and hopefully a subset of haskell. Provided our > objectives, the old Haskell parser written in Java would be a very > good starting point. Where can I find it? It is in the older versions, starting from 0.4. Each of them includes the sources, so you can just download and unzip from plugins/de.leiffrenzel.fp.haskell.source_x.y.z..jar/src/parsersrc.zip. Thanks && ciao, Leif > > Upon prototype completion, I will publish a report about its > development and the main concerns I may have found. > > Good luck for us, > > Thiago Arrais > thi...@gm... > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput > a projector? How fast can you ride your desk chair down the office luge track? > If you want to score the big prize, get to know the little guy. > Play to win an NEC 61" plasma display: http://www.necitguy.com/?r > _______________________________________________ > eclipsefp-develop mailing list > ecl...@li... > https://lists.sourceforge.net/lists/listinfo/eclipsefp-develop > > |