"Ian D. Stewart" <[EMAIL PROTECTED]> writes:
> First off, apologies if this is not an appropriate forum for this
> question.
Completely appropriate.
> I've been going over the header files generated by javah to make sure
> the contain all the necesarry entries for the particular native
> methods. I've noticed that, in addition to some of the headers missing
> entries for native methods, there is at least one (java_lang_Object.h)
> that contains entries for non-native methods.
>
> >From what I understand, missing entries for the native methods is a Bad
> Thing(TM). My question is, is there any potential harm that could be
> caused by the entries for non-native methods, or is it safe to leave
> them in?
As long as the function is not called in a way which would require it
to be defined I don't see how it would matter to have extra
declarations. Those sorts of things should be bugs in the javah
program in question though, right?
I think the method by which we compile would cause gcc to spit out
errors for functions which are defined without a previous declaration
but I could be wrong on that.
Brian
--
Brian Jones <[EMAIL PROTECTED]>
