> I'm still hoping to hear from Guillem and Thomas to see if adding string.h > makes sense for memset and memcpy, but be that as it may, does anyone see an > issue with replacing all instances of bzero/bcopy with memset/memcpy ?
That seems fine. We avoided that sort of thing in the past to minimize divergence from other Mach variants. But there aren't really any others any more, so obvious cleanups of 15-year-old cruft is fine. _______________________________________________ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd
