News for hackers. Stuff that matters.

A comment on How an Engineering Company Chose to Migrate to D. Parent comment

Re:How an Engineering Company Chose to Migrate to D by steveklabnik on Wednesday June 20, 2018 @05:57PM (#17360173)
It’s a pointer to the environment, and a pointer to the function. So yes, not a stack frame pointer.

The environment is a struct containing what is captured; so for example, it would contain an &T if your closure captures a T by reference. You don’t need to walk a set of stack pointers to find it, just follow the reference directly there.

[ Parent | on HN ]
Re:How an Engineering Company Chose to Migrate to D by WalterBright on Wednesday June 20, 2018 @06:27PM (#17360405)
That's distinctly different from D's, which has a pointer to the enclosing stack frame.

If it is the enclosing function, it's just a single pointer to it. The "walking" comes from if you're accessing the enclosing function's enclosing function's frame.

[ Parent | on HN ]
Re:How an Engineering Company Chose to Migrate to D by steveklabnik on Wednesday June 20, 2018 @07:34PM (#17360857)
Makes perfect sense, thanks. I’m now wondering about the trade offs of these two approaches...
[ Parent | on HN ]