iceytomatoes t1_jbaa2po wrote
i still don't understand this since the last time you posted it
is the readme in examples supposed to be empty
lurgi t1_jbarw1b wrote
It looks like it takes the file containing the function, slaps an int main()
in there which calls the function with the appropriate arguments, and then compiles and runs the code. No values can be returned from the function and my guess is it will only work with a few data types (int, float, char, maybe string) so good luck using anything remotely interesting.
iceytomatoes t1_jbaw9rn wrote
i understand it gets a little complicated depending on what's being returned, but for returning values wouldn't it be feasible to wrap that in an input()?
lurgi t1_jbawg6k wrote
If what you are returning can easily be represented as a string, I suppose you could.
ragtagthrone t1_jbbla1i wrote
So in theory you could stringify any object and return that as long as you have a deserialization step to handle it.
lurgi t1_jbbp5gi wrote
Then you'd need to modify the C/C++ code so that it doesn't return a Widget
type or whatever and instead serializes the data in such a way that it can be deserialized by the caller.
At this point it's just FFI with me doing all the work. Plus, every time a function is called with different arguments, the C compiler is invoked (this also means whoever is running the code will need a C compiler installed, which seems like a big ask).
ragtagthrone t1_jbbx4sf wrote
Yeah, seems really rigid tbh
Viewing a single comment thread. View all comments