The tooling for debugging is still growing. Gallium.jl with Juno is nice, but I still do a lot of println debugging. As Gallium/Juno matures I use it more and more often.
To make sure you're not using old versions, quit the REPL. In Juno, that's Ctrl+j Ctrl+k. You can hit that command almost instantly, and if you have the process server enabled (which I think will be introduced and be the default in the next version they are tagging?) then Juno already has a process started that is waiting for you, so there is no delay after doing this. Since there's really no delay, I do this after every Pkg.update(), most of the time when things need to re-compile (you can specifically highlight and evaluate a method to recompile it, but I find that quitting the REPL like this is so easy that I tend to overuse it), or just out of caution I'll use it. Another Juno command which is good to know is Ctrl+j Ctrl+c which will clear the console. On Friday, September 16, 2016 at 12:19:08 AM UTC-7, Tsur Herman wrote: > > Thank you for the time you took to answer. > > How do you go about debugging and inspecting? and making sure that changes > you made gets compiled > and that you are not accidentally running a previously imported version of > a function? > > > On Thursday, September 15, 2016 at 10:11:21 PM UTC+3, Tsur Herman wrote: >> >> Hi , I am new here . >> Just started playing around with julia, my background is in Matlab c++ >> and GPU computing(writing kernels) >> >> I am trying to figure out what will be good practice for rapid >> prototyping. >> How would you use Julia and Juno IDE for a research and development >> project that will >> end up having numerous files and many lines of code , and a basic gui? >> >> Please share your experience , thanks. >> Tsur >> >> >>
