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
I just noticed, that the functions generated by getC.jl package generate untyped function parameters, whereas I typed the function parameters.
Leaving the types away is quite convenient, as all the annoying type conversions are done by ccall.
Maybe I should do the same, even though it feels very odd, to have such a low level api untyped (even though, that the ccall does the type check in the end).
This also means, that you could override glCalls, by supplying a function with correctly typed parameters.
Guess I should just leave the types away for now, until I find a good solution for this.
The text was updated successfully, but these errors were encountered:
I just noticed, that the functions generated by getC.jl package generate untyped function parameters, whereas I typed the function parameters.
Leaving the types away is quite convenient, as all the annoying type conversions are done by ccall.
Maybe I should do the same, even though it feels very odd, to have such a low level api untyped (even though, that the ccall does the type check in the end).
This also means, that you could override glCalls, by supplying a function with correctly typed parameters.
Guess I should just leave the types away for now, until I find a good solution for this.
The text was updated successfully, but these errors were encountered: