From: Tom Tromey <tom@tromey.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Burgess <aburgess@redhat.com>, binutils@sourceware.org
Subject: Re: [PATCH] bfd: make _bfd_section_size_insane part of the public API
Date: Wed, 10 Jan 2024 10:54:18 -0700 [thread overview]
Message-ID: <87v881rs51.fsf@tromey.com> (raw)
In-Reply-To: <0c54069e-d907-4f03-8d7f-15374d4bfd6a@suse.com> (Jan Beulich's message of "Fri, 5 Jan 2024 13:03:50 +0100")
>>>>> "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
prev parent reply other threads:[~2024-01-10 17:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 16:15 Andrew Burgess
2024-01-02 11:21 ` Ping: " Andrew Burgess
2024-01-05 12:03 ` Jan Beulich
2024-01-10 11:03 ` Andrew Burgess
2024-01-10 12:47 ` Jan Beulich
2024-01-10 13:48 ` Andrew Burgess
2024-01-10 14:26 ` Jan Beulich
2024-01-10 16:20 ` Andrew Burgess
2024-01-10 21:22 ` Alan Modra
2024-01-11 8:23 ` Jan Beulich
2024-03-06 11:17 ` Andrew Burgess
2024-03-06 11:30 ` Jan Beulich
2024-03-25 18:33 ` Andrew Burgess
2024-01-10 17:54 ` Tom Tromey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v881rs51.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).