Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
I need to use droidtext (http://code.google.com/p/droidtext/) in my project but am hitting a lot of cases where field names are like the following: "_3D". The bindings try to generate a property name "3D" for this which gets us into trouble. I think that instead the bindings should keep the leading underscore if a number immediately follows it.
For Android API bindings such names that begin with a number are forced to be explicitly named manually, like android/view/KeyEvent.KEYCODE_3D_MODE field becomes enum value Keycode.ThreeDMode (not Keycode.3DMode which is invalid). I don't think our naming of fields are not very simple to introduce such special escaping. Also at least we believed that there shouldn't be such a lot of "public" fields whose name begin with _.
I think it shouldn't be very difficult to create such a java tool that iterates all the fields in all the classes and generate part of Metadata.xml so far.
I agree that naming fields beginning with _ is stupid. I guess it's not a big deal because as you say there shouldn't be too many of them and we can explicitly rename them.
We now output warnings. https://github.com/xamarin/java.interop/pull/69