News for hackers. Stuff that matters.

A comment on Show HN: “Nim in Action” is now available. Parent comment

Re:Show HN: “Nim in Action” is now available by SeanDav on Thursday January 28, 2016 @02:31PM (#10990561)
A major concern to me is how to Debug Nim. Considering it compiles into C as a first step, I would have thought that Debugging may have quite a few issues and gotchas as well as some good tips and tricks.

I am not sure if this is covered, but did not notice it mentioned in the contents.

[ Parent | on HN ]
Re:Show HN: “Nim in Action” is now available by gokr on Thursday January 28, 2016 @02:40PM (#10990637)
Debugging via gdb and frontends using gdb like KDevelop or QtCreator works very well - except data drilling. But that may be solved eventually.
[ Parent | on HN ]
Re:Show HN: “Nim in Action” is now available by z92 on Thursday January 28, 2016 @07:50PM (#10992725)
But gdb probably will point to C source line instead of nim's source. That might be a problem.
[ Parent | on HN ]
Re:Show HN: “Nim in Action” is now available by gokr on Thursday January 28, 2016 @08:07PM (#10992787)
No, you get Nim source code debugging using line number directives etc, works great including breakpoints and all. I have tested several IDEs and it works. But data inspection does generally not work - that would require some work to support GDB protocols.
[ Parent | on HN ]
Re:Show HN: “Nim in Action” is now available by stevedonovan on Friday January 29, 2016 @01:35AM (#10993846)
Fortunately, GDB is scriptable in Python. The C++ add-ons make life so much easier, no reason it can't be done for Nim.
[ Parent | on HN ]
Re:Show HN: “Nim in Action” is now available by dom96 on Thursday January 28, 2016 @07:07PM (#10992573)
This will be covered as part of Chapter 5.
[ Parent | on HN ]