[PATCH] bfd: make _bfd_section_size_insane part of the public API

[Tom Tromey]

>>>>> "Jan" == Jan Beulich <jbeulich@suse.com> writes:

Jan> Having seen your ping (and no other response), let me share my view:
Jan> This function implements a certain policy, internal to the library.
Jan> By exposing it, you would make external users dependent upon this
Jan> specific policy. What if later we change our view on what's "insane"?
Jan> IOW external consumers want to implement their own, independent policy
Jan> (if so desired).

Merely exposing the API does not require any BFD user to actually call
it.

Furthermore it seems fine if it changes.  And, if it isn't fine in some
case, then that situation can be addressed when this actually happens.
TBH This seems unlikely to me and anyway doesn't seem like a very strong
reason to prevent the function from being made public.

Tom