Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>I've come to the conclusion that C is best understood if you think about it in terms of the way that an assembly language programmer would think about doing things

I agree with this. I found another article that made the transition for someone coming from something like Python or Ruby easier. It shows how to use gdb as a sort of C REPL. https://www.recurse.com/blog/5-learning-c-with-gdb

The quick feedback loop certainly makes things like pointers, arrays, etc, more clear.



Wow. I've been flirting around with learning C for awhile now (coming from a couple dynamic languages, including python), and this is by far the most helpful read about pointers I've ever come across. Thanks a ton.




Heck yeah. Thanks for the tip. Btw, new link is here:

https://github.com/zsaleeba/picoc


+1 to this. GDB and valgrind are the best things about writing C.


Valgrind is the best thing since sliced bread - saved me so much time and agony...


One things that I've found enlightening is when you have an IDE that allows you to step through mixed source and assembly. You can see your data being slopped around and processed. (int a = 10; becomes ld R4,10)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: