FYI, the standard way around this is to expose a "free" method from your DLL for memory allocated by the DLL. The other way is to require that users of the DLL supply the memory in advance to functions needing it. These two methods are the ones used by the Windows libraries themselves. Pretty standard stuff. One other possibility might be to register some sort of callback from the C++ code that the go DLL code can call to allocate memory from the C++ space. But I would not prefer that.
Good Luck. On Friday, May 25, 2018 at 2:35:19 PM UTC-4, Liron Levy wrote: > > Gotcha :) > > Thanks for the info, guess i will have to find a way around it then. At > least i now know there is no real way to do what i wanted so that close > this door :) > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
