Handle @Annotated parameters when generating JNI headers from Java.

base/android/jni_generator/jni_generator.py

Index: base/android/jni_generator/jni_generator.py
diff --git a/base/android/jni_generator/jni_generator.py b/base/android/jni_generator/jni_generator.py
index 4e700feab5e12dcd9983c80554a7c06d0ac53907..7982797266130f7553e241bc38ef20a3616c4b4c 100755
--- a/base/android/jni_generator/jni_generator.py
+++ b/base/android/jni_generator/jni_generator.py
@@ -356,8 +356,14 @@ class JniParams(object):
     ret = []
     for p in [p.strip() for p in params.split(',')]:
       items = p.split(' ')
+
+      # Remove @Annotations from parameters.
+      if items[0][0] is '@':

[PEConn, 2016/08/23 15:30:12]

It'd be really cool if we could do some magic that converts the int to an
appropriate enum if this is a Java annotation generated from a C++ enum.

[Bernhard Bauer, 2016/08/23 15:33:08]

Hm, but we only use @IntDef enums, which are just integers under the hood
anyway.

[Torne, 2016/08/23 15:40:03]

I'd prefer "if items[0].startswith('@')" - and also can't there be more than one
annotation? (and parameters to the annotation and so on?) Making this fully
general is probably a pain I guess..

And yes, it'd be nice to handle enums/etc properly; if some feels like
implementing that later go ahead ;p

[Bernhard Bauer, 2016/08/25 10:29:05]

OK, I'm now handling any number of annotations, but no parameters yet. Yes, at
some point it would probably start making more sense to use a proper Java
parser.

+        del items[0]
+
       if 'final' in items:
         items.remove('final')
+
       param = Param(
           datatype=items[0],
           name=(items[1] if len(items) > 1 else 'p%s' % len(ret)),