You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'd like to request that either this is clarified in the documentation. On this page here, it mentions that you can pass e.g. “System.Object:GetHashCode()” into mono_method_desc_new() to help you search for a method. I think it would be helpful to clarify that you also need to specify what arguments the function takes. For example, if this function took an int parameter, it would need to say “System.Object:GetHashCode(int)”. A lot of the info at the top of here should probably also be mentioned. In particular the fact that floats need to be written as "single" to find the correct method.
I also think it should be mentioned that mono_method_desc_new() allocates memory and needs to be freed with mono_method_desc_free(). I'm unsure if mono_jit_cleanup () will automatically get rid of allocated mono memory and would appreciate this being cleared up.
The text was updated successfully, but these errors were encountered:
Hi, I'd like to request that either this is clarified in the documentation. On this page here, it mentions that you can pass e.g. “System.Object:GetHashCode()” into mono_method_desc_new() to help you search for a method. I think it would be helpful to clarify that you also need to specify what arguments the function takes. For example, if this function took an int parameter, it would need to say “System.Object:GetHashCode(int)”. A lot of the info at the top of here should probably also be mentioned. In particular the fact that floats need to be written as "single" to find the correct method.
I also think it should be mentioned that mono_method_desc_new() allocates memory and needs to be freed with mono_method_desc_free(). I'm unsure if mono_jit_cleanup () will automatically get rid of allocated mono memory and would appreciate this being cleared up.
The text was updated successfully, but these errors were encountered: