Ruby Under a Microscope: Learning Ruby Internals through Experiment
patshaughnessy.net
Ruby Under a Microscope: Learning Ruby Internals through Experiment
1–10 of 40 posts
Re: Ruby Under a Microscope: Learning Ruby Internals through Experiment
#2Re: Ruby Under a Microscope: Learning Ruby Internals through Experiment
#3Thanks for posting this :) ...I'm happy to answer any questions anyone has.
Re: Ruby Under a Microscope: Learning Ruby Internals through Experiment
#4Thanks for posting this :) ...I'm happy to answer any questions anyone has.
Hey pat, how do you understand the internal code so well ? I read your free chapter on Ruby's Hash table and I loved every bit of it. It would be great if you can share the process you go through when you read the source code, so maybe I can apply it in the future. By the way, congrats for the release !
Re: Ruby Under a Microscope: Learning Ruby Internals through Experiment
#5Re: Ruby Under a Microscope: Learning Ruby Internals through Experiment
#6Because I've already learned so much from this articles, I was eager to buy this when I saw the announcement in my inbox.
Re: Ruby Under a Microscope: Learning Ruby Internals through Experiment
#7Re: Ruby Under a Microscope: Learning Ruby Internals through Experiment
#8Thanks for posting this :) ...I'm happy to answer any questions anyone has.
Hey pat, how do you understand the internal code so well ? I read your free chapter on Ruby's Hash table and I loved every bit of it. It would be great if you can share the process you go through when you read the source code, so maybe I can apply it in the future. By the way, congrats for the release !
A lot of hard work! I do the hard work so you don't have to :)
Re: Ruby Under a Microscope: Learning Ruby Internals through Experiment
#9Earlier quoted context omitted.
Hey pat, how do you understand the internal code so well ? I read your free chapter on Ruby's Hash table and I loved every bit of it. It would be great if you can share the process you go through when you read the source code, so maybe I can apply it in the future. By the way, congrats for the release !
Hey thanks for asking - and yes, in the preface to the book I do explain how I figure this stuff out. But basically I: - study the C code for a long time - step through it in GDB a lot - add printf statements and recompile it to print out debug/trace info - actually change it to see what would happen if things were written differently. A lot of hard work! I do the hard work so you don't have to :)