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

LuaWrapper: Use the correct index when storing a function #4775

Merged
merged 2 commits into from
Jan 13, 2017

Conversation

rgacogne
Copy link
Member

Short description

The LuaWrapper used to assume that the function was at the top of the stack, making it effectively impossible to have a callback function parameter anywhere else than as the last parameter.

Checklist

I have:

The LuaWrapper used to assume that the function was at the
top of the stack, making it effectively impossible to have
a callback function parameter anywhere else than as the last
parameter.
@@ -1642,10 +1642,10 @@ class LuaContext {
// structure that will ensure that a certain is stored somewhere in the registry
struct ValueInRegistry {
// this constructor will clone and hold the value at the top of the stack in the registry
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comment is now wrong?

@@ -1642,10 +1642,10 @@ class LuaContext {
// structure that will ensure that a certain is stored somewhere in the registry
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comment already was wrong ;)

@pieterlexis pieterlexis merged commit 75226d5 into PowerDNS:master Jan 13, 2017
@rgacogne rgacogne deleted the luawrapper-func-index branch January 13, 2017 13:54
pieterlexis added a commit that referenced this pull request Feb 16, 2017
Backport #4775: LuaWrapper: Use the correct index when storing a function
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants