I'm opposed to nested includes because it makes it difficult to diagnose
include ordering violations but I realize that's a losing battle.

  I actually wonder why hardly anybody uses the '%I' format instead 
  which util/snprintf.c understands - perhaps because a move to IPv6 (if 
  ever) would be more complicated?

I suspect snprintf was added after most of these callers were written to use
inet_ntoa.  They could safely be changed now but no one has bothered.
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info

Reply via email to