Hello folks,
Working on some code involving FFI calls to a Rust dylib, I found out that it
seems that returns values get eaten now.
Of course, almost the same code was working a week ago. In between, I optimised
my Rust code a lot and upgraded my MacOs to Sierra. Just today I returned to
work in the Racket side.
I checked that the rust code is working ok and indeed it is. However, the
_string I'm getting back in Racket is now always "". Note that my Rust code
receives and processes its inputs perfectly well as I can log to stdout the
various steps of processing without any alteration. Only the return value seems
weird.
For the most polyglot of you, the last two lines of the rust function invoked
are:
println!("[RUST] {}", rret);
CString::new(rret).unwrap().as_ptr()
And the println! shows the correct value (and the CString... was working well
before I upgrade, I'm pretty sure of that).
I upgraded Racket to version 6.6, same result and before I tear apart all the
code in both sides of my FFI, I wanted to know if anyone could confirm FFI is
still working on MacOS Sierra.
Thanks!
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
