Work to prepare for the debugger has been going on in Base all along, DWARF.jl, and Keno also has stuff that he has not yet committed. He’ll send details when he has something for everyone to try out.
The first step is to get a working debugger. Once we have a debugger, the plan is to start integration with both Eclipse and Juno, but we haven’t yet figured out how easy or difficult it will be. I suspect it won’t be too difficult. -viral > On 10-Mar-2016, at 3:41 PM, Andreas Lobinger <lobing...@gmail.com> wrote: > > Afaics Gallium.jl is a thin layer on some other debugging/compiling > infrastructure. The main work is not in Gallium.jl iself, but in the lower > layers. > > On Thursday, March 10, 2016 at 10:45:15 AM UTC+1, DNF wrote: > On Thursday, March 10, 2016 at 7:00:46 AM UTC+1, Viral Shah wrote: > This is about the right time to start the triage for the various 0.5 issues. > With all the amazing compiler improvements, LLVM upgrade, Cxx readiness, > thread-safety (will probably remain disabled for 0.5 potentially unless it > receives significant testing) and a number of other cool things, I agree with > Stefan here that we should not wait for array views for 0.5, but certainly > include all the other array changes. Also, we are working hard towards having > a debugger ready, which potentially could be the last major feature before > calling feature freeze. > > By debugger, do you mean Gallium.jl? I have occasionally taken a look at the > repository, and got the impression that it was not very active. > > A debugger for Julia would be the most amazing thing! It is the single most > important missing feature that is holding me back from using Julia in my > day-to-day work. Have you any idea if it would be long before the debugger > could be integrated in the IDEs (Juno/Eclipse)?
