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

use mono/linker sources to build the linker #291

Merged
merged 1 commit into from Nov 11, 2016

Conversation

radekdoulik
Copy link
Contributor

  • recently the linker was moved out of mono to a standalone
    repository, so update XA to use the sources from the new location

 - recently the linker was moved out of mono to a standalone
   repository, so update XA to use the sources from the new location
@jonpryor jonpryor merged commit 3c55f93 into xamarin:master Nov 11, 2016
radical pushed a commit that referenced this pull request May 8, 2018
While reviewing cd50ef2 it occurred to us that
`JniNativeMethodRegistrationArguments` is a *`struct`*. As such, it
has a default constructor, which `null`-initializes things.

Which in turn means that *all* properties, at present, can be `null`.

Thus, a question: *Is this a problem*? Specifically, would it be a
problem if `JniNativeMethodRegistrationArguments.Registrations`
were `null`?

Turns Out™ that there are many places which assume that it is *not*
`null`, such as `JavaProxyObject.RegisterNativeMembers()`.

Update `JniNativeMethodRegistrationArguments.Registrations` so that
when `_registrations` is `null` we throw `InvalidOperationException`.
This will avoid `NullReferenceExceptions`.
@github-actions github-actions bot locked and limited conversation to collaborators Feb 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants