-
Notifications
You must be signed in to change notification settings - Fork 550
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
Call BigDecimal(num) instead of BigDecimal.new(num) #928
Conversation
Turns out I was chasing a NULL pointer on cBigDecimal from statement.c when I removed the class lookup from result.c, extern meant the compiler did not flag an uninitialized value.
Thanks for the fix. I have verified It would be appreciated the new version of mysql2 gem released to support Ruby 2.5 which is scheduled to release on 12/25. Thanks again for the fix. |
I can backport the deprecation warning fix to 0.4.x as well in January, there no other issue on Ruby 2.5 besides this warning.
|
Sounds good. 0.4.x including this fix is fine for me. |
@sodabrew it seems the above has not happened yet |
Call BigDecimal(num) instead of BigDecimal.new(num) to be ready for this deprecation in Ruby 2.6, and eliminate a deprecation warning now. Reduce the number of extern classes - while developing this change, I was chasing a NULL pointer on cBigDecimal from statement.c because I removed the class lookup from result.c, but extern meant the compiler did not flag it as an uninitialized value.
Resolves #925