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

fixed direct-mapping type-mapped pointer result types #319

Merged
merged 3 commits into from
May 13, 2014

Conversation

marco2357
Copy link
Contributor

As described/discussed/requested in #317


// Can't extend java.awt.Point; can't add:
// public final static TypeMapper TYPE_MAPPER = mapper;
// -> Extend Native.options via reflection:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Were these other issues you ran into? Could you please elaborate?

@marco2357
Copy link
Contributor Author

I changed the test to use an own Point class that provides a TYPE_MAPPER. It's true that Native.register should be improved, but that should be tackled independently.

@marco2357
Copy link
Contributor Author

bump

twall added a commit that referenced this pull request May 13, 2014
fixed direct-mapping type-mapped pointer result types
@twall twall merged commit 5115f14 into java-native-access:master May 13, 2014
twall added a commit that referenced this pull request May 13, 2014
mstyura pushed a commit to mstyura/jna that referenced this pull request Sep 9, 2024
Motivation:

We should use the latest netty release

Modifications:

Update to 4.1.67.Final

Result:

Use latest netty release
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.

2 participants