Skip to content

Deal with ABI requirements for function names #1448

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Dushistov opened this issue Apr 11, 2017 · 0 comments
Open

Deal with ABI requirements for function names #1448

Dushistov opened this issue Apr 11, 2017 · 0 comments

Comments

@Dushistov
Copy link

I like restriction of 100 characters maximum for line length,
and I want force this restriction to my code, but I cann't.

My function should have such name Java_net_akaame_project_packet_LibraryService_subscribeOnUpdates__Lnet_akaame_project_packet_InfoLoggerAsync_2

this is external restriction I can not change. This is part is restriction of ABI of Oracle's Java virtual machine,
I have java code like this:

package net.akaame.project.packet;

class LibraryService {
public native void subscribeOnUpdates(InfoLoggerAsync obj);
}

and to have ability connect my rust and java code I have name function in such way.

But it's length exceed 100 characters maximum. So --write-mode diff return error,

so it would be nice add ability to force 100 characters maximum, except pub, #[no_mangle] function names.

I suppose my use case not unique, for example in plugin development,
you may also have similar requirment for function names.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants