Re: stdbit-h, stdc_*: New modules, part of the stdbit module
Collin Funk wrote: > Maybe it makes sense to provided a module covering all the stdbit.h > functions? Yes. That's why I wrote: We thus have the following modules: - stdbit-h for just the header file, - stdc_* for the 14 function groups, - stdbit for all together. < > Also, should these functions be used to implement the count-* versions > used previously and ffs, ffsl, ffsll? That way any optimization > wizardry can be dealt with in a single place and benefit them all. It might make sense. Paul, if it is among your plans to do this, how about letting Collin do it? This would give Collin some more exercise with the Gnulib idioms. Bruno
Re: stdbit-h, stdc_*: New modules, part of the stdbit module
Hi Bruno, On 5/15/24 4:06 PM, Bruno Haible wrote: > The module 'stdbit' defines 70 functions, grouped into 14 function-like > macros. Most packages will only need 1 or 2 among these 14 function groups. > (For example, diffutils needs only 'stdc_bit_width'.) Maybe it makes sense to provided a module covering all the stdbit.h functions? I can see a program wanting a majority/all of them and in that case it might be nicer just to import a single module. Also, should these functions be used to implement the count-* versions used previously and ffs, ffsl, ffsll? That way any optimization wizardry can be dealt with in a single place and benefit them all. Collin
