ALLOW_C_FUNCTION's first parameter doesn't seem very helpful

[Julian Waters]

Hi everyone,

I couldn't help but notice that the method name passed to the macro to
allow use of itself isn't really needed in any way. Comments in the macro
definition say it's to show exactly what method is being permitted by the
macro, but to me it seems the actual call to it that happens in the second
half of the macro already does that job entirely

// It's already obvious from the actual method call itself that we want
std::_Exit
ALLOW_C_FUNCTION(::_Exit, ::_Exit(code);)

Is there a reason we still keep the first parameter around other than for
documentation purposes?

best regards,
Julian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/hotspot-dev/attachments/20230402/8f27ca6e/attachment.htm>