On Thu, Mar 24, 2011 at 6:45 PM, Kevin Polulak <[email protected]> wrote: > What I would like to know is: what new features would you like to see in the > new debugger? Yesterday, plobsing mentioned something about a REPL and I > think this would be a nice addition as well. However, I don't have any > experience them. In spite of this fact, I don't think it's entirely out of > my league as I do have time before the summer to get my hands dirty. Though > I think it's important to consider this: is two months enough time for me to > become more familiar with REPL's and is three months enough time to > implement it into the Parrot debugger while leaving enough time for other > features?
I mentioned this in IRC earlier, but want to re-emphasize it. A debugger project can really be a big project, and there are always more features you can add. Depending on who you ask, the list of "necessary" features can be unmanageably large. REPL is one of those interesting features that is nice to have and some people would really appreciate, but represents a huge amount of work. This project will be large already, and there are always more features to add so we can fill up the time if you magically finish the core parts early. Worrying about any one individual feature is not nearly so important right now as planning and designing a stable, maintainable, robust debugger framework. When GSoC is over, and you're up to your eyebrows in schoolwork again, we need a system that other developers can easily jump into and start working on without you. Or, if you can still squeeze in some Parrot time next fall, you can lead a team of people to grow it bigger and faster than one person could ever do alone. A REPL is something we could add if we had a good framework to build on and if we can solve some of the higher-level problems. The important part is that good framework. --Andrew Whitworth _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
