PHXH
/
hybridclr_unity
53
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[change] changed from throw exception to logError when not supported pinvoke or reverse pinvoke method parameter type was found

main
walon 2025-06-06 16:57:53 +08:00
parent 56486b8a76
commit c9ff293dfe
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Editor/MethodBridge/MonoPInvokeCallbackAnalyzer.cs
View File

@ -55,7 +55,7 @@ namespace HybridCLR.Editor.MethodBridge
}
if (!MetaUtil.IsSupportedPInvokeMethodSignature(method.MethodSig))
{
throw new Exception($"MonoPInvokeCallback method {method.FullName} has unsupported parameter or return type. Please check the method signature.");
Debug.LogError($"MonoPInvokeCallback method {method.FullName} has unsupported parameter or return type. Please check the method signature.");
}
//foreach (var ca in method.CustomAttributes)
//{

2
Editor/MethodBridge/PInvokeAnalyzer.cs
View File

@ -38,7 +38,7 @@ namespace HybridCLR.Editor.MethodBridge
{
if (!MetaUtil.IsSupportedPInvokeMethodSignature(method.MethodSig))
{
throw new Exception($"PInvoke method {method.FullName} has unsupported parameter or return type. Please check the method signature.");
Debug.LogError($"PInvoke method {method.FullName} has unsupported parameter or return type. Please check the method signature.");
}
_pinvokeMethodSignatures.Add(new CallNativeMethodSignatureInfo { MethodSig = method.MethodSig });
}