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

need explicit function call for c_long_double #3990

Merged
merged 1 commit into from
Sep 15, 2014

Conversation

WalterBright
Copy link
Member

Supplemental needed for dlang/druntime#958

Yes, this makes it a regression, but an unavoidable one.

@9rnsr
Copy link
Contributor

9rnsr commented Sep 15, 2014

Auto-merge toggled on

9rnsr added a commit that referenced this pull request Sep 15, 2014
need explicit function call for c_long_double
@9rnsr 9rnsr merged commit 73bb17a into dlang:master Sep 15, 2014
@dnadlinger
Copy link
Member

So now we go out and tell everybody to change all their C API? Somehow, just making real 64 bit on Win64 (and maybe providing a special __real80 type or whatever) just seems a lot more attractive.

@WalterBright
Copy link
Member Author

So now we go out and tell everybody to change all their C API?

This has always been true for Win64. It's why we have c_long_double.

Somehow, just making real 64 bit on Win64 (and maybe providing a special __real80 type or whatever) just seems a lot more attractive.

But what about the poor saps who need higher precision and have the hardware for it? If others are happy with 64 bit precision, they can use double and be done with it.

@d-random-contributor
Copy link

They would
import core.hw : float80;

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

Successfully merging this pull request may close these issues.

4 participants