Bug 10657 - Need a way to prevent `ListenerImplementor` generation.
Summary: Need a way to prevent `ListenerImplementor` generation.
Status: RESOLVED INVALID
Alias: None
Product: Android
Classification: Xamarin
Component: Bindings ()
Version: 4.5.x
Hardware: PC Mac OS
: Low enhancement
Target Milestone: master
Assignee: Atsushi Eno
URL:
Depends on:
Blocks:
 
Reported: 2013-02-25 15:46 UTC by Jonathan Pryor
Modified: 2016-09-22 07:53 UTC (History)
3 users (show)

Tags: XATriaged
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 INVALID

Description Jonathan Pryor 2013-02-25 15:46:05 UTC
Context: http://forums.xamarin.com/discussion/comment/5711/#Comment_5711

(Theoretical?) Problem: if a "Listener" interface is a non-public type, we can't implement it from our normal ACW generated code.

We may want to add an attribute that the generator could look for to inhibit generation of the ListenerImplementor type (and thus prevent the type from being used for events?).

For that matter, It'll be ~impossible to implement ANY nested type with a non-public accessibility! We should probably think about how to fix that...
Comment 1 Atsushi Eno 2016-09-22 07:53:34 UTC
There is no chance that non-public interface get public API exposure in C# unless you make visibility wrong. And such changes should be out of our support scope.