@matigo Just wait till they find out what happened to Fortran with Fortran 90.
/@nitinkhanna @gtwilson
@nitinkhanna I just get annoyed every time I have to fill out both City+State and Zip. At least infer State given the other two!
@streakmachine Homebrew works well. You can also use PkgSrc if you have that NetBSD craving.
@JeremyCherfas Ah, good on Atom!
And that makes sense about not troubling with a debugger just yet. Good to know what tools could help should you run into a thornier problem in future.
@matigo The display resolution and battery life on paper is just out of this world.
/@sumudu @gtwilson
@JeremyCherfas An IDE that understands code references can help a lot with chasing those down. That helps you map out data flow and the effect of any changes.
For crashers or understanding a failing computation, a good tool to have is a debugger. That should let you set a breakpoint / trigger the debugger, which halts the program and lets you nose around in the memory, call functions, etc. Basically, stop the world and have a look around. Often you can arrange to have it run under the debugger and automatically stop when a crash happens anywhere or exception gets thrown.