Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

typo #5

Open
Jared-Prime opened this issue Nov 12, 2012 · 1 comment
Open

typo #5

Jared-Prime opened this issue Nov 12, 2012 · 1 comment

Comments

@Jared-Prime
Copy link

But alongside YARV’s internal stack Ruby also keeps track of your Ruby program’s call stack: which methods called which other methods, functions, blocks, lambdas, etc. In fact, YARV is not just a stack machine – it’s a “double stack machine!” It not only has to track the arguments and return values for it’s own internal instructions; it has to do it for your Ruby arguments and return values as well.

Pat Shaughnessy. Ruby Under a Microscope (Kindle Locations 1079-1082).

Should the first sentence read: "alongside YARV's internal stack YARV also keeps track of your Ruby's program's call stack", or am I misreading?

@patshaughnessy
Copy link
Owner

I tend to use "YARV" and "Ruby" interchangeably, at least in this chapter. I suppose this could be a bit misleading. Maybe I can rewrite that sentence...?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants