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

DWORD_PTR is defined as Pointer instead of an Word #99

Closed
AndreasPK opened this issue Feb 19, 2018 · 2 comments · Fixed by #100
Closed

DWORD_PTR is defined as Pointer instead of an Word #99

AndreasPK opened this issue Feb 19, 2018 · 2 comments · Fixed by #100

Comments

@AndreasPK
Copy link

Current Behavior

This is currently defined as a Ptr, however according to MSDN:
1
2

It's a 32/64 bit long unsigned Integer.

Currently it's defined as a Ptr to a Word32 value.

Mistuke added a commit to Mistuke/win32 that referenced this issue Feb 19, 2018
@Mistuke Mistuke mentioned this issue Feb 19, 2018
8 tasks
Mistuke added a commit that referenced this issue Feb 19, 2018
@Mistuke Mistuke added this to the 2.6.3.0 milestone Feb 19, 2018
@Mistuke
Copy link
Contributor

Mistuke commented Feb 19, 2018

Thanks!

@AndreasPK
Copy link
Author

Correct me if I'm wrong but as far as I can tell it shouldn't be a Pointer at all but rather a pointer sized Integer.

a3f added a commit to a3f/ghc-win32 that referenced this issue Feb 19, 2018
MSDN notes: typedef ULONG_PTR DWORD_PTR;
@a3f a3f mentioned this issue Feb 19, 2018
8 tasks
a3f added a commit to a3f/ghc-win32 that referenced this issue Feb 20, 2018
MSDN notes: typedef ULONG_PTR DWORD_PTR;
Mistuke pushed a commit that referenced this issue Feb 20, 2018
MSDN notes: typedef ULONG_PTR DWORD_PTR;
bgamari pushed a commit to bgamari/win32 that referenced this issue Sep 10, 2020
Fixes haskell#21, which noted that the `LICENSE` file was inconsistent with
`License: BSD3` in the .cabal` file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants