[mono-android] Why "Seppuku" ?

2013-09-27 Thread Samus Arin
I've been poking around the ACW source java files and came across the file Seppuku. I always see a logcat entry for this during process startup, and was wondering why it is named as such. Is there any significance, or is it just a codename ? Thanks! -- View this message in context: http://mo

[mono-android] Java .class operator support in JNI/JNIEnv ?

2013-09-27 Thread Samus Arin
Using JNI/JNIEnv, is it possible to execute the second statement (.class operator) ? Class[] paramTypes= new Class[1]; paramTypes[0]= String.class; If so, and anyone knows of the top of their head, could I maybe see a quick sketch please ? Thanks. -- View this message in context: htt

Re: [mono-android] Java .class operator support in JNI/JNIEnv ?

2013-09-27 Thread Samus Arin
After all this work, the property debug.mono.extra doesn't even exist, arr (ah well): IntPtr ptrSystemProperties = JNIEnv.FindClass("android/os/SystemProperties"); IntPtr ptrObject = JNIEnv.GetObjectClass(ptrSystemProperties); IntPtr method = JNIEnv.GetStaticMethodID(pt

Re: [mono-android] Why "Seppuku" ?

2013-09-27 Thread Jonathan Pryor
On Sep 27, 2013, at 11:58 AM, Samus Arin wrote: > I always see a logcat entry for this during process startup, and was > wondering why it is named as such. mono.android.Seppuku is a broadcast receiver which calls java.lang.Runtime.exit(); you can view obj\Debug\android\src\mono\android\Seppuku

Re: [mono-android] Java .class operator support in JNI/JNIEnv ?

2013-09-27 Thread Jonathan Pryor
On Sep 27, 2013, at 12:33 PM, Samus Arin wrote: > Using JNI/JNIEnv, is it possible to execute the second statement (.class > operator) ? The `.class` operator is equivalent to the C# `typeof` operator. Depending on what you need to do with it, you can either use typeof(T) directly, or you can

Re: [mono-android] Java .class operator support in JNI/JNIEnv ?

2013-09-27 Thread Jonathan Pryor
On Sep 27, 2013, at 4:56 PM, Samus Arin wrote: > After all this work, the property debug.mono.extra doesn't even exist, Why are you checking for the debug.mono.extra property? It's cleared by the debugger as part of startup; even if you did see it as a non-empty string, it wouldn't remain non-e