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
The generated JNI code will end up scoping the references twice (example error):
javacpp_test/test/jniNested.cpp:297:101: error: no member named 'com' in 'com::company::NestedTest'; did you mean simply 'com'?
static void JavaCPP_test_Nested_00024NestedTest_00024ListenerInternal_deallocate(void *p) { delete (::com::company::NestedTest::com::company::NestedTest::Listener*)p; }
If the original class is in the global namespace, the rename works correctly.
I'm attaching a trivial example that recreates the issue. Run build.sh in the root directory.
Consider the following class:
If a rule is added to the parser as follows:
The generated JNI code will end up scoping the references twice (example error):
If the original class is in the global namespace, the rename works correctly.
I'm attaching a trivial example that recreates the issue. Run build.sh in the root directory.
javacpp_test.tar.gz
The text was updated successfully, but these errors were encountered: