-
-
Notifications
You must be signed in to change notification settings - Fork 328
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
Rename function to prevent conflict to debase #443
Rename function to prevent conflict to debase #443
Conversation
e34239a
to
f0e9366
Compare
Makes sense to me @tzmfreedom! I guess you could potentially bundle both debuggers (for example, |
ext/byebug/byebug.h
Outdated
@@ -125,7 +125,7 @@ extern VALUE next_thread; | |||
|
|||
/* functions from context.c */ | |||
extern void Init_context(VALUE mByebug); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You need to replace this function as well, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your review. I fixed it.
2421388
to
8cbe292
Compare
Thank you @tzmfreedom! |
When we use byebug and debase gem simultaneously, there are conflict because extern function name is conflict each other.
For example, with byebug and debase gem, if we use
byebug
method to debug code, the following error is occured (this is the same issue as #200 #360 )This is because both gem have extern function
Init_context
andcontext_create
and if we call these function in byebug gem, it calls debase's function. (Maybe other development gem use these function name, becausecontext
is commonly used variable name)This PR solve by renaming function.