Two years of Rust

Re:Two years of Rust by yorwba on Monday May 15, 2017 @11:33PM (#14347180)

I use gdb as a C REPL. You attach it to a binary that has the functions you need, then you can use them with the `p` (or `print`) command. Loops and new function definitions are not possible, but sometimes it's still good enough.

[ Parent | on HN ]

Re:Two years of Rust by RhysU on Tuesday May 16, 2017 @07:54AM (#14348858)

Gdb as REPL is a nice trick. Beaker Notebook might give the notebook parent wants for C work.

[ Parent | on HN ]

Re:Two years of Rust by photojosh on Wednesday May 17, 2017 @09:09PM (#14364155)

Thanks. It won't since all my C work is embedded and mainly systems programming rather than algorithms. But I'll keep it in mind for the next time I have to translate my Python explorations over to C for production.

[ Parent | on HN ]

Re:Two years of Rust by photojosh on Wednesday May 17, 2017 @09:04PM (#14364131)

Good point. I've only been working with AVRs for a few years since I've been at this job, but looks like it might be doable. Thanks for the tip.

[ Parent | on HN ]

Re:Two years of Rust by pjmlp on Tuesday May 16, 2017 @02:49AM (#14347829)

That is how I once developed a B+ Tree library for low level disk blocks back in 1996, it was quite helpful tracking down how the nodes were being used.

[ Parent | on HN ]