Skip to content

Conversation

@andyundso
Copy link
Member

@andyundso andyundso commented Sep 28, 2023

From my understanding, you only need to define an alloc function if you want to define a C struct and store values on it. For example, TinyTds::Client defines such an allocate function to wrap its client. On TinyTds::Result, it does not seem we do have a struct and therefore does not need an alloc function.

Closes #515

From my understanding, you only need to define an `alloc` function if you want to define a C struct and store values on it. For example, `TinyTds::Client` defines such an `allocate` function to wrap its client. On `TinyTds::Result`, it does not seem we do have a struct and therefore does not need an `alloc` function.
@andyundso andyundso requested a review from aharpervc September 28, 2023 16:15
@aharpervc
Copy link
Contributor

I assume that the warning from #515 is no longer showing with this?

@andyundso
Copy link
Member Author

Exactly. You can compare the output on the Ruby 3.2 job on the current master and this branch, and you see that the warning no longer shows on the very top of the output.

@andyundso andyundso merged commit e60b00a into rails-sqlserver:master Sep 28, 2023
@andyundso andyundso deleted the undefined-alloc branch September 28, 2023 20:26
@Michoels
Copy link

Looks great!
When will this be released?

@taylorthurlow
Copy link

Looks great! When will this be released?

This looks like it went out with v2.1.6 in early December.

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

Successfully merging this pull request may close these issues.

Ruby 3.2 warning: undefining the allocator of T_DATA class TinyTds::Result

4 participants