For smaller C programs I've made good use of include-what-you-use[1]
Given the size and length of time this code has been around, I thought it might be worth a go against the OpenAFS code.
It might identify some interesting bits or clarify the include order of things.
Pat [1] https://github.com/include-what-you-use/include-what-you-use https://koji.fedoraproject.org/koji/packageinfo?packageID=19950 https://packages.ubuntu.com/bionic/iwyu -- Pat Riehecky Fermi National Accelerator Laboratory www.fnal.gov www.scientificlinux.org _______________________________________________ OpenAFS-devel mailing list OpenAFS-devel@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-devel
