Bug 629 - A couple of methods should have [NullAllowed]
Summary: A couple of methods should have [NullAllowed]
Status: RESOLVED FIXED
Alias: None
Product: MonoMac
Classification: Desktop
Component: Bindings ()
Version: GIT
Hardware: Macintosh Mac OS
: --- minor
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2011-09-04 18:09 UTC by Eric Smith
Modified: 2012-02-09 14:45 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Eric Smith 2011-09-04 18:09:14 UTC
A very minor annoyance, but a couple of methods are missing [NullAllowed] annotations for some of their parameters:

At maccore/src/foundation.cs, line 4020:
NSUrl GetUrl (NSSearchPathDirectory directory, NSSearchPathDomain domain, 
[NullAllowed] NSUrl url, bool shouldCreate, out NSError error);


At monomac/src/appkit.cs, line 12557:
void OrderOut ([NullAllowed] NSObject sender);
Comment 1 Miguel de Icaza [MSFT] 2012-02-09 14:45:51 UTC
The second change makes me wonder if we are allowed to in general pass nulls to anything that follows the pattern with "NSObject sender"