References: <7c847a1e-32fb-6b09-9886-1ea5ec7f7015@isc.org> X-Mailer: MIME-tools 5.508 (Entity 5.508) X-RT-Interface: Web Message-ID: X-RT-Original-Encoding: utf-8 Content-Transfer-Encoding: binary MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Content-Type: text/plain; charset="utf-8" RT-Send-CC: Content-Length: 881 On Wed Nov 29 21:51:48 2017, ray wrote: > On 29/11/2017 18:11, Michał Kępień via RT wrote: > > > Correct, but I failed to find a better term and "callback" should give > > the reader the right idea. Plain "function" sounds too generic to me. > > If you have any suggestions, I am all ears (or you can even push a > > relevant tweak to the branch if you feel like it, as far as I am > > concerned). > > "Callback" is already in common parlance in many cases when a function > pointer is being passed even for immediate use, rather than asynchronously. It's no biggie, but overloading terms will usually hit you sooner or later (like passing the callback data as one "pointer", because it's what you usually do). But let's not spend more time than needed here - I can add this to some list for all hands when/if we discuss the coding style. So we are done with this for now.