-
Notifications
You must be signed in to change notification settings - Fork 153
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
Possible for --with-attribute to allow for multiple =
in args?
#469
Comments
Right after typing this I figured out that the key is meant to be what you are binding the attribute to, and the value is the actual attribute. However I'm still running into issues because I have the constructor for the attribute that needs to be passed in for the array. I think it's a parsing issue re this:
Other ways to get around it could be positional params, but the ctor for the attribute has no params so you have to do a field assignment inline. I understand why you want to bail on more than 2 |
=
in args?
I'm fine with a contribution that changes this to split on the first |
Sounds great, made a PR here: |
Allow equals sign in value for parsed KVP Pairs
Resolved with #471 |
Hello! Trying to annotate some output functions with an additional attribute, specifically:
UnmanagedCallersOnly(CallConvs = new[] { typeof(CallConvCdecl) })
or something similar.
However, no matter what I try to pass to --with-attribute this either doesn't work because the program expects a key/value(?) or it generates the proper bindings but there is no attribute output. I also looked into the TerraFX interop rsp examples where you bind to Flags but I'm still unclear on what that's doing/why attributes need a key/value configuration when I assume they should just be copy-pasted strings, as well as what the key/value would be in my case.
The text was updated successfully, but these errors were encountered: