You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, modifying autogenned code is obviously not the right approach. How can I tell c-for-go to not copy the buffer but rather just use the array pointer?
Thanks!
The text was updated successfully, but these errors were encountered:
Hi! Thank you for your work on c-for-go. We're using it to generate go bindings for the uldaq library. Here's the function that gives us issues:
https://github.com/mccdaq/uldaq/blob/1d8404159c0fb6d2665461b80acca5bbef5c610a/examples/DInScan.c#L150
ulDInScan collects data from the data acquisition device and saves it into the provided buffer.
When we generate bindings for ulDInScan, the buffer "data" gets the following treatment in autogenned go code:
...but the provided data array never gets populated
I searched for similar patterns and found one here: https://github.com/5k3105/nidaq/blob/d33879c3427eb8b59a08a65a41edd3ad00459e85/nidaqmx.go#L1482C19-L1482C113
and in this case, the provided array is simply passed along as a pointer.
I modified the autogenned go code for ulDInScan to mimic the link above:
...and it works great!
However, modifying autogenned code is obviously not the right approach. How can I tell c-for-go to not copy the buffer but rather just use the array pointer?
Thanks!
The text was updated successfully, but these errors were encountered: