-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
COM: TYPEFLAGS constants missing?! #615
Comments
Please contribute, see https://github.com/java-native-access/jna/blob/master/www/Contributing.md. |
I will try... but first I fear that I need some excercises in git... :-] |
These might be better defined within an interface rather than a class.
|
Oh... ok... I thought that is dealt as antipattern? (Effective Java, Item 19). On the job we try to avoid the constants in interface-pattern. Or are there some special architectural specialties in jna I don't know yet? |
Kind of preachy, that. That item actually recommends adding constants to the class or interface to which they are tightly bound. In this case, that'd probably be the Structure that uses them.
|
Yeah, perhaps you are right (with the "preachy"). |
#619 pull request created... I have corrected compile errors in the contribution projects as well and have adapted the .project- and .classpath-files for eclipse |
#615: added TYPEFLAGS constants for TYPEATTR in ITypeInfo.GetTypeAttr()
Motivation: We should be able to support connection migration the server side. This can be tested via quiche: ``` cargo run --bin quiche-client -- --no-verify --perform-migration https://127.0.0.1:9999/` ``` Modifications: Be able to support migrations by offering the remote peer connection ids to use. Result: Be able to do connection migration in all cases.
Hi there, in the type
TYPEATTR
is the attributewTypeFlags
. I have not found a declaration of these constants?! (info based on jna 4.2.1)After reading the msdn library this would be my suggestion:
The text was updated successfully, but these errors were encountered: