Bug 1846 - remove extraneous I prefix on interface names
Summary: remove extraneous I prefix on interface names
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 2.0
Hardware: PC Mac OS
: --- enhancement
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-11-03 03:40 UTC by Atsushi Eno
Modified: 2012-04-18 06:01 UTC (History)
1 user (show)

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:

Description Atsushi Eno 2011-11-03 03:40:16 UTC
I came across interfaces named IButtonListener, IJoystickListener, IStreamConnector etc. (com.zeemote.zc.event in Zeemote SDK, http://www.zeemote.com/). When they are mapped to managed interface, they become IIButtonListener, IIJoystickListener and IIStreamConnector and so on, which does not make sense.

I can fix the naming itself, but there is a blocking issue: we somehow premises that Java interfaces are *never* prefixed (actually the premise is kind of worse: "there won't be any type that has IXxx and Xxx"). When there is ISomeInterface which contain some consts, there will be C# ISomeInterface *class* that is to contain corresponding managed fields. But the name is for the interface itself (when this issue gets fixed) and there is no room for the abstract class.
Comment 1 Atsushi Eno 2012-04-18 06:01:13 UTC
Fixed. In case it gets stuck by name conflict explained above, metadata fixup should be available.