-
Notifications
You must be signed in to change notification settings - Fork 37
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
C INT_MAX not handled #204
Comments
I believe s/INT_MAX/int.max/ does the job for the first error. |
ciechowoj
added a commit
to ciechowoj/dstep
that referenced
this issue
Sep 29, 2018
There was a bug preventing dstep from including |
The bindnings in druntime solves this by naming the type |
ciechowoj
added a commit
to ciechowoj/dstep
that referenced
this issue
Sep 30, 2018
ciechowoj
added a commit
to ciechowoj/dstep
that referenced
this issue
Oct 2, 2018
ciechowoj
added a commit
to ciechowoj/dstep
that referenced
this issue
Oct 2, 2018
ciechowoj
added a commit
to ciechowoj/dstep
that referenced
this issue
Oct 5, 2018
ciechowoj
added a commit
to ciechowoj/dstep
that referenced
this issue
Dec 31, 2018
jacob-carlborg
added a commit
that referenced
this issue
Dec 31, 2018
Fix #204: C INT_MAX not handled.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using DStep v0.2.3-16-g1308991 compiled on Debian Sid with LDC 1.11.0 and LLVM 6.0, I generated a module for fontconfig.h (version 2.13.0). Sadly:
I am not sure where the
stat_
is creeping in. The generated D is:The text was updated successfully, but these errors were encountered: