Bug 2626 - btouch generates duplicate definitions
Summary: btouch generates duplicate definitions
Status: RESOLVED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: 5.0
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Sebastien Pouliot
URL:
Depends on:
Blocks:
 
Reported: 2011-12-23 15:54 UTC by James Clancey
Modified: 2012-01-27 09:56 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 James Clancey 2011-12-23 15:54:06 UTC
When you bind something that has 2 similar properties. You get the following error.

		[Export ("save")]
		bool Save ();

		[Export ("save:")]
		bool Save (NSError error);


The type `Parse.PFFile' already contains a definition for `selSave'
Comment 1 Sebastien Pouliot 2012-01-22 11:29:53 UTC
`btouch` SelectorField method does not create unique name with the selector ends with a ':' character.

The btouch fix can be easy (e.g. add a '_' to selectors ending with ':') but it requires to update all the non-generated code in monomac.dll and monotouch.dll (64 errors) to use the new selector names. OTOH it should have no impact outside the assemblies since the static fields are all private.

An alternative would be to build a selector name cache... but that will only slow down the tool without any real gain (now or later).
Comment 2 Sebastien Pouliot 2012-01-27 09:56:40 UTC
generator fixed in 392640d77498953b140b6713387bc9bdc85e563e
manual bindings in maccore fixed in 017c3946f89848e3c1c0cefe1e17e1d170ef2dfd