Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Untyped vs Typed parameter #1

Open
SimonDanisch opened this issue Apr 7, 2014 · 1 comment
Open

Untyped vs Typed parameter #1

SimonDanisch opened this issue Apr 7, 2014 · 1 comment
Assignees

Comments

@SimonDanisch
Copy link
Member

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.

@rennis250
Copy link

I tried in the past in failed. Let me know how it goes!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants